Ping: [PATCH, testsuite] ignore some "conflicting types for built-in" messages
Jeff Law
law@redhat.com
Fri Nov 9 20:57:00 GMT 2018
On 11/9/18 7:21 AM, Paul Koning wrote:
> Ping.
>
> I'd like to commit this. The discussion seems to have ended up with the conclusion that this is a reasonable approach.
>
> paul
>
>
>> On Nov 1, 2018, at 3:13 PM, Paul Koning <paulkoning@comcast.net> wrote:
>>
>> A number of test cases contain declarations like:
>> void *memcpy();
>> which currently are silently accepted on most platforms but not on all; pdp11 (and possibly some others) generate a "conflicting types for built-in function" warning.
>>
>> It was suggested to prune those messages because the test cases where these occur are not looking for the message but are testing some other issue, so the message is not relevant. The attached patch adds dg-prune-output directives to do so.
>>
>> Ok for trunk?
>>
>> paul
>>
>> ChangeLog:
>>
>> 2018-11-01 Paul Koning <ni1d@arrl.net>
>>
>> * gcc.dg/Walloca-16.c: Ignore conflicting types for built-in
>> warnings.
>> * gcc.dg/Wrestrict-4.c: Ditto.
>> * gcc.dg/Wrestrict-5.c: Ditto.
>> * gcc.dg/pr83463.c: Ditto.
>> * gcc.dg/torture/pr55890-2.c: Ditto.
>> * gcc.dg/torture/pr55890-3.c: Ditto.
>> * gcc.dg/torture/pr71816.c: Ditto.
OK. Thanks for being patient with the round and round on this one.
jeff
More information about the Gcc-patches
mailing list