public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: FX Coudert <fxcoudert@gmail.com>
To: gcc-patches@gcc.gnu.org
Subject: Testsuite: fix contructor priority test
Date: Sat, 19 Aug 2023 22:40:28 +0200	[thread overview]
Message-ID: <F1FF1B0D-C401-4C51-8134-A54CAAE9180E@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 114 bytes --]

Bordering on obvious, tested on darwin where the test case fails before (and now passes).

OK to commit?
FX


[-- Attachment #2: 0001-Testsuite-fix-contructor-priority-test.patch --]
[-- Type: application/octet-stream, Size: 1052 bytes --]

From 24f2425675f888155cda7f8fcbddeda52ce272b7 Mon Sep 17 00:00:00 2001
From: Francois-Xavier Coudert <fxcoudert@gcc.gnu.org>
Date: Sat, 19 Aug 2023 22:37:33 +0200
Subject: [PATCH] Testsuite: fix contructor priority test

Fix the expected warning wording for targets without constructor
priority, like Darwin, making the test pass.

gcc/testsuite/ChangeLog:

	PR testsuite/111066
	* g++.dg/special/initpri3.C: Fix wording.
---
 gcc/testsuite/g++.dg/special/initpri3.C | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

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 }
-- 
2.39.2 (Apple Git-143)


             reply	other threads:[~2023-08-19 20:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-19 20:40 FX Coudert [this message]
2023-09-03 13:36 ` FX Coudert

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=F1FF1B0D-C401-4C51-8134-A54CAAE9180E@gmail.com \
    --to=fxcoudert@gmail.com \
    --cc=gcc-patches@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).