public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Jonathan Yong <jyong@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-6414] gcc.dg/memchr-3.c: Account for LLP64 warnings Date: Thu, 2 Mar 2023 13:42:09 +0000 (GMT) [thread overview] Message-ID: <20230302134209.D098138582AB@sourceware.org> (raw) https://gcc.gnu.org/g:62a8d31ecc07041af4a81353c2d57d9845c4b771 commit r13-6414-g62a8d31ecc07041af4a81353c2d57d9845c4b771 Author: Jonathan Yong <10walls@gmail.com> Date: Mon Feb 27 10:02:32 2023 +0000 gcc.dg/memchr-3.c: Account for LLP64 warnings gcc/testsuite/ChangeLog: PR middle-end/97956 * gcc.dg/memchr-3.c (memchr): Account for LLP64 warnings. Signed-off-by: Jonathan Yong <10walls@gmail.com> Diff: --- gcc/testsuite/gcc.dg/memchr-3.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 {
reply other threads:[~2023-03-02 13:42 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230302134209.D098138582AB@sourceware.org \ --to=jyong@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ /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: linkBe 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).