On 04/11/2018 11:20 PM, Martin Sebor wrote:
> On 04/11/2018 06:47 AM, Andreas Krebbel wrote:
>> On 04/11/2018 10:02 AM, Jakub Jelinek wrote:
>>> On Wed, Apr 11, 2018 at 09:48:05AM +0200, Andreas Krebbel wrote:
c-c++-common/attr-nonstring-3.c fails on IBM Z. The reason appears to be
that
On 04/11/2018 06:47 AM, Andreas Krebbel wrote:
On 04/11/2018 10:02 AM, Jakub Jelinek wrote:
On Wed, Apr 11, 2018 at 09:48:05AM +0200, Andreas Krebbel wrote:
c-c++-common/attr-nonstring-3.c fails on IBM Z. The reason appears to be
that we provide builtin implementations for strcpy and stpcpy.
On 04/11/2018 10:02 AM, Jakub Jelinek wrote:
> On Wed, Apr 11, 2018 at 09:48:05AM +0200, Andreas Krebbel wrote:
>> c-c++-common/attr-nonstring-3.c fails on IBM Z. The reason appears to be
>> that we provide builtin implementations for strcpy and stpcpy. The
>> warnings currently will only be
On Wed, Apr 11, 2018 at 09:48:05AM +0200, Andreas Krebbel wrote:
> c-c++-common/attr-nonstring-3.c fails on IBM Z. The reason appears to be
> that we provide builtin implementations for strcpy and stpcpy. The
> warnings currently will only be emitted when expanding these as normal
> calls.
>
>
c-c++-common/attr-nonstring-3.c fails on IBM Z. The reason appears to be
that we provide builtin implementations for strcpy and stpcpy. The
warnings currently will only be emitted when expanding these as normal
calls.
Bootstrapped and regression tested on x86_64 and s390x.
Ok?
gcc/ChangeLog: