This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC 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: Lessons learned from compiler error/warnings tests


On 09/09/16 13:28, Florian Weimer wrote:
For compile-time fortify checks (such as the wrappers for type-safe
open/openat), we need to add tests in glibc which examine the compiler output
for warnings and errors.

I do not want to add Dejagnu as a dependency to the glibc test suite, but I
wonder if you could share any lessons learned from the testing support facility
in GCC.

That seems wise. Ian words may be worth taking into account:
http://www.airs.com/blog/archives/499

and do not miss the comment by Joel Brobecker about what AdaCore uses (internally?).


Would you suggest to mirror the GCC directives exactly?

I find the GCC directives easy to read and use. There are some quirks, like the need to specify all no-op options such as "{ *-*-* }" just to provide an explicit line-number. And it would be useful to have additional directives that compile the tests with different options (we have many many duplicated tests that only differ in the options or directives). But your parser does not need to have those limitations.

Cheers,
	Manuel.


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