From: Jonathan Wakely <jwakely@redhat.com>
To: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Cc: Thomas Rodgers <trodgers@redhat.com>
Subject: [committed] libstdc++: Add missing space after effective-target name in test
Date: Thu, 16 Feb 2023 11:49:24 +0000 [thread overview]
Message-ID: <20230216114924.108222-1-jwakely@redhat.com> (raw)
In-Reply-To: <20230216114016.105674-1-jwakely@redhat.com>
I only noticed this when sending the mail for he previous commit.
Tested x86_64-linux and pushed to trunk.
-- >8 --
libstdc++-v3/ChangeLog:
* testsuite/17_intro/names_pstl.cc: Add space after effective
target name.
---
libstdc++-v3/testsuite/17_intro/names_pstl.cc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libstdc++-v3/testsuite/17_intro/names_pstl.cc b/libstdc++-v3/testsuite/17_intro/names_pstl.cc
index e5f3ca91aa2..42ce098550c 100644
--- a/libstdc++-v3/testsuite/17_intro/names_pstl.cc
+++ b/libstdc++-v3/testsuite/17_intro/names_pstl.cc
@@ -1,5 +1,5 @@
// { dg-do compile { target c++17 } }
-// { dg-additional-options "-DTBB_SUPPRESS_DEPRECATED_MESSAGES=1" { target tbb_backend} }
+// { dg-additional-options "-DTBB_SUPPRESS_DEPRECATED_MESSAGES=1" { target tbb_backend } }
// The TBB headers use non-reserved names (because they're not part of the
// implementation) so we need to include them before the macro definitions
--
2.39.1
next prev parent reply other threads:[~2023-02-16 11:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 11:40 [committed] libstdc++: Fix non-reserved names in PSTL headers Jonathan Wakely
2023-02-16 11:49 ` Jonathan Wakely [this message]
2023-02-16 12:40 ` [committed] libstdc++: Make names_pstl.cc require et tbb_backend Jonathan Wakely
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=20230216114924.108222-1-jwakely@redhat.com \
--to=jwakely@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.org \
--cc=trodgers@redhat.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).