public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kip at thevertigo dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/101228] #include <execution> triggers Intel TBB warning for tbb/task.h
Date: Sun, 27 Jun 2021 02:49:34 +0000	[thread overview]
Message-ID: <bug-101228-4-ierqwwM4ku@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101228-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from Kip Warner <kip at thevertigo dot com> ---
Suggestion: Maybe a unit test that includes all the standard STL headers, does
nothing with them, and that's expected to emit no warnings would mitigate
problems like this occurring in the future.

  reply	other threads:[~2021-06-27  2:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-27  1:13 [Bug libstdc++/101228] New: " kip at thevertigo dot com
2021-06-27  2:49 ` kip at thevertigo dot com [this message]
2021-06-27  3:22 ` [Bug libstdc++/101228] tbb/task.h is Deprecated in newer TBB pinskia at gcc dot gnu.org
2021-06-28  0:59 ` kip at thevertigo dot com
2021-06-28  9:09 ` redi at gcc dot gnu.org
2021-06-28  9:32 ` doko at debian dot org
2021-06-28  9:36 ` redi at gcc dot gnu.org
2021-06-28 11:47 ` pilarlatiesa at gmail dot com
2021-06-28 13:29 ` redi at gcc dot gnu.org
2021-06-28 17:23 ` rodgertq at gcc dot gnu.org
2022-05-27  9:01 ` pilarlatiesa at gmail dot com
2022-05-27 10:03 ` redi at gcc dot gnu.org
2022-10-30 14:13 ` hicham at mouline dot org
2022-11-18 20:10 ` kerukuro at gmail dot com
2023-02-16 11:24 ` redi at gcc dot gnu.org
2023-06-27 14:48 ` redi at gcc dot gnu.org
2024-02-29 11:27 ` redi at gcc dot gnu.org
2024-03-19 16:00 ` 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-101228-4-ierqwwM4ku@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).