public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc r13-6082] libstdc++: Make names_pstl.cc require et tbb_backend
Date: Thu, 16 Feb 2023 12:39:07 +0000 (GMT)	[thread overview]
Message-ID: <20230216123907.A38C83858D33@sourceware.org> (raw)

https://gcc.gnu.org/g:7478278f88ba1753e68d6962b7f38d1be5b43d56

commit r13-6082-g7478278f88ba1753e68d6962b7f38d1be5b43d56
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Thu Feb 16 12:18:25 2023 +0000

    libstdc++: Make names_pstl.cc require et tbb_backend
    
    The https://github.com/oneapi-src/oneTBB/pull/833 fix is needed for TBB
    headers to avoid an error with GCC 13. The new names_pstl.cc test needs
    to check effective target tbb_backend so that it's UNSUPPORTED on
    systems without fixed headers.
    
    libstdc++-v3/ChangeLog:
    
            * testsuite/17_intro/names_pstl.cc: Require et tbb_backend.

Diff:
---
 libstdc++-v3/testsuite/17_intro/names_pstl.cc | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/libstdc++-v3/testsuite/17_intro/names_pstl.cc b/libstdc++-v3/testsuite/17_intro/names_pstl.cc
index 42ce098550c..019e4774ff2 100644
--- a/libstdc++-v3/testsuite/17_intro/names_pstl.cc
+++ b/libstdc++-v3/testsuite/17_intro/names_pstl.cc
@@ -1,10 +1,12 @@
 // { dg-do compile { target c++17 } }
-// { dg-additional-options "-DTBB_SUPPRESS_DEPRECATED_MESSAGES=1" { target tbb_backend } }
+// { dg-require-effective-target tbb_backend }
+// { dg-add-options no_pch }
 
 // 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
 // in names.cc:
 #if __has_include(<tbb/tbb.h>)
+# define TBB_SUPPRESS_DEPRECATED_MESSAGES 1
 # include <tbb/tbb.h>
 #endif
 // Now we can define the macros to poison uses of non-reserved names:

                 reply	other threads:[~2023-02-16 12:39 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=20230216123907.A38C83858D33@sourceware.org \
    --to=redi@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    --cc=libstdc++-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).