public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-6428] testsuite: Fix up memchr-3.c test [PR108991]
Date: Thu,  2 Mar 2023 23:51:10 +0000 (GMT)	[thread overview]
Message-ID: <20230302235110.7175A3858CDB@sourceware.org> (raw)

https://gcc.gnu.org/g:73bbfd5970ba3b7a5bcb3f7043d93fec89ccb991

commit r13-6428-g73bbfd5970ba3b7a5bcb3f7043d93fec89ccb991
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Fri Mar 3 00:50:10 2023 +0100

    testsuite: Fix up memchr-3.c test [PR108991]
    
    The newly added dg-warning directive was missing the comment argument,
    so the target selector was treated as comment and the warning was expected
    on all targets when it should be expected only on llp64 targets.
    
    2023-03-03  Jakub Jelinek  <jakub@redhat.com>
    
            PR testsuite/108991
            * gcc.dg/memchr-3.c: Add missing comment argument to dg-warning
            before target selector.

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 af1b26ef3ae..9c73265a89e 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); /* { dg-warning "-Wbuiltin-declaration-mismatch" { target llp64 } } */
+extern void* memchr (const void*, int, long); /* { dg-warning "-Wbuiltin-declaration-mismatch" "" { target llp64 } } */
 
 struct SX
 {

                 reply	other threads:[~2023-03-02 23:51 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=20230302235110.7175A3858CDB@sourceware.org \
    --to=jakub@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: 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).