Lessons learned from compiler error/warnings tests

Florian Weimer fweimer@redhat.com
Fri Sep 9 12:29:00 GMT 2016

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.

Would you suggest to mirror the GCC directives exactly?

I probably have to implement the testing directive parser as a small C 


More information about the Gcc mailing list