This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFA] Fix setting of VSX registers


> One approach would be to refactor these procs so that your use can work.
> I think this would be nice to have -- I think it would be good to have
> fewer boilerplate tests with "synthetic" names, ones that nobody is
> interested in.

When we discussed the new gdb-testsuite that AdaCore uses, we talked
about that quite a bit. And unsurprisingly, there was no obvious answer.
These tests can be an annoyance if all hell breaks lose and they all
start to fail. A PASS indeed adds little value to the results.  But
on the other hand, I have always felt that we should verify that these
commands have the expected results, and that we should get a FAIL if
we detect something went wrong. Ideally, we wanted to be able to group
a sequence of commands as one "setup phase" and generate one FAIL if
part of the sequence fails. But in the end, we decided that it was just
simpler to treat everything as a test (this is what I have pretty much
done in dejagnu as well).

-- 
Joel


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]