This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Lessons learned from compiler error/warnings tests
- From: Manuel López-Ibáñez <lopezibanez at gmail dot com>
- To: Florian Weimer <fweimer at redhat dot com>, GCC <gcc at gcc dot gnu dot org>
- Cc: GNU C Library <libc-alpha at sourceware dot org>
- Date: Fri, 9 Sep 2016 19:15:44 +0100
- Subject: Re: Lessons learned from compiler error/warnings tests
- Authentication-results: sourceware.org; auth=none
- References: <29835506-6a1a-d0f4-ff70-01e298928dd1@redhat.com>
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.