Lessons learned from compiler error/warnings tests

[Mikhail Maltsev]

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:
> http://www.airs.com/blog/archives/499
> 
> and do not miss the comment by Joel Brobecker about what AdaCore uses
> (internally?).
> 
> 
And probably this talk is also somewhat relevant (Cauldron 2013 - DejaGNU BOF):
https://www.youtube.com/watch?v=rjm-n9EgxiE

-- 
Mikhail Maltsev