From: Jonathan Yong <10walls@gmail.com>
To: Jonathan Yong via Gcc-patches <gcc-patches@gcc.gnu.org>,
richard.sandiford@arm.com
Subject: Re: [Patch] gcc.dg/memchr-3.c: fix for LLP64
Date: Thu, 2 Mar 2023 13:43:30 +0000 [thread overview]
Message-ID: <51b54f05-f6d6-fbb1-9f5a-987e47264a1d@gmail.com> (raw)
In-Reply-To: <mpth6v3jurg.fsf@arm.com>
On 3/2/23 10:46, Richard Sandiford wrote:
>> diff --git a/gcc/testsuite/gcc.dg/memchr-3.c b/gcc/testsuite/gcc.dg/memchr-3.c
>> index c38d9cf3349..af1b26ef3ae 100644
>> --- a/gcc/testsuite/gcc.dg/memchr-3.c
>> +++ b/gcc/testsuite/gcc.dg/memchr-3.c
>> @@ -6,7 +6,7 @@
>> typedef __INT8_TYPE__ int8_t;
>> typedef __INT32_TYPE__ int32_t;
>>
>> -extern void* memchr (const void*, int, long);
>> +extern void* memchr (const void*, int, long); /* { dg-warning "-Wbuiltin-declaration-mismatch" { target llp64 } } */
>>
>> struct SX
>> {
>
> OK, thanks.
>
> Richard
Thanks, pushed to master branch.
next prev parent reply other threads:[~2023-03-02 13:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 10:09 Jonathan Yong
2023-02-27 16:55 ` Richard Sandiford
2023-03-01 13:41 ` Jonathan Yong
2023-03-02 10:46 ` Richard Sandiford
2023-03-02 13:43 ` Jonathan Yong [this message]
2023-03-02 23:52 ` [committed] testsuite: Fix up memchr-3.c test [PR108991] Jakub Jelinek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51b54f05-f6d6-fbb1-9f5a-987e47264a1d@gmail.com \
--to=10walls@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.sandiford@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).