On Mon, 14 Jan 2019, Jeff Law wrote: > On 1/14/19 9:39 AM, Paolo Carlini wrote: > > Hi, > > > > On 14/01/19 17:28, Jakub Jelinek wrote: > >> I think several testcases check for duplicate error messages, the > >> regexp is > >> against the whole text, so you can just check if it occurs more than once > >> there. > > > > This is essentially https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30612 > Anyone working in this space should probably look at Ian's blogpost. > > https://www.airs.com/blog/archives/499
Also in the July 2013 discussion (starting at <https://gcc.gnu.org/ml/gcc/2013-07/msg00398.html> I listed a series of other issues with DejaGnu - especially that neither DejaGnu nor the test code in GCC should need to know anything at all about how to make pieces of an uninstalled toolchain find each other, that should be entirely the responsibility of "make install". To the issues added there I should also add: the DejaGnu board file interface is insufficiently expressive. Specifically, it only supports tests exiting with a DejaGnu status rather than an arbitrary exit code, which is an issue if you want to use DejaGnu board files with a non-DejaGnu testsuite (so that the board interaction code only has to be written once) - it's perfectly possible to construct a DejaGnu "testsuite" that takes externally provided tests to run on the board (and for that matter to compile, if you wish to reuse ldscript settings from the board file by compiling through DejaGnu), and so use a board file for a non-DejaGnu testsuite, but that testsuite can't get back any extra information it might want from test exit statuses. -- Joseph S. Myers jos...@codesourcery.com
