public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/111066] g++.dg/special/initpri3.C fails on darwin
Date: Fri, 18 Aug 2023 17:54:57 +0000	[thread overview]
Message-ID: <bug-111066-4-v4esNulNK4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111066-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111066

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
The wording of the warning is different from what dg-warning directive in the
testcase expects.

diff --git a/gcc/testsuite/g++.dg/special/initpri3.C
b/gcc/testsuite/g++.dg/special/initpri3.C
index 3d745a42a6a..63ed3208228 100644
--- a/gcc/testsuite/g++.dg/special/initpri3.C
+++ b/gcc/testsuite/g++.dg/special/initpri3.C
@@ -7,4 +7,4 @@
 #endif

 struct A { A(); } a __attribute__((init_priority(500)));
-// { dg-warning "attribute directive ignored" "" { target { ! init_priority }
} .-1 }
+// { dg-warning "attribute ignored" "" { target { ! init_priority } } .-1 }


Is the correct fix I think. The directive in the warning only comes from
namespace and using uses.

  parent reply	other threads:[~2023-08-18 17:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-18 17:42 [Bug c++/111066] New: " fxcoudert at gcc dot gnu.org
2023-08-18 17:44 ` [Bug c++/111066] " fxcoudert at gcc dot gnu.org
2023-08-18 17:54 ` pinskia at gcc dot gnu.org [this message]
2023-08-19 20:41 ` [Bug testsuite/111066] " fxcoudert at gcc dot gnu.org
2023-11-03 13:22 ` fxcoudert at gcc dot gnu.org
2024-04-02 18:47 ` cvs-commit at gcc dot gnu.org

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=bug-111066-4-v4esNulNK4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).