This is the mail archive of the
mailing list for the GCC project.
Re: Lessons learned from compiler error/warnings tests
- From: Mikhail Maltsev <maltsevm at gmail dot com>
- To: Manuel López-Ibáñez <lopezibanez at gmail dot com>, 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: Sat, 10 Sep 2016 00:06:40 +0300
- Subject: Re: Lessons learned from compiler error/warnings tests
- Authentication-results: sourceware.org; auth=none
- References: <firstname.lastname@example.org> <email@example.com>
On 09.09.2016 21:15, Manuel López-Ibáñez wrote:
> 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:
> and do not miss the comment by Joel Brobecker about what AdaCore uses
And probably this talk is also somewhat relevant (Cauldron 2013 - DejaGNU BOF):