public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pilarlatiesa at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/113376] Confusing notes when using C++17 parallel algorithms Date: Mon, 15 Jan 2024 15:13:39 +0000 [thread overview] Message-ID: <bug-113376-4-akUuP0akX4@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113376-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113376 --- Comment #3 from Pilar Latiesa <pilarlatiesa at gmail dot com> --- It seems that what is missing is a corresponding change in the macro definition logic. It should have been changed to: // Check the user-defined macro for warnings #if defined(PSTL_USAGE_WARNINGS) # define _PSTL_USAGE_WARNINGS #endif See https://github.com/llvm/llvm-project/blob/5ccf19ded09f68bef43275c81c20b0e65f7c0b75/pstl/include/pstl/internal/pstl_config.h#L26
next prev parent reply other threads:[~2024-01-15 15:13 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-13 13:04 [Bug libstdc++/113376] New: " pilarlatiesa at gmail dot com 2024-01-13 14:26 ` [Bug libstdc++/113376] " redi at gcc dot gnu.org 2024-01-15 8:50 ` pilarlatiesa at gmail dot com 2024-01-15 10:17 ` redi at gcc dot gnu.org 2024-01-15 15:13 ` pilarlatiesa at gmail dot com [this message] 2024-01-15 16:05 ` redi at gcc dot gnu.org 2024-06-12 10:48 ` redi at gcc dot gnu.org 2024-06-12 10:56 ` redi at gcc dot gnu.org 2024-06-12 11:22 ` [Bug libstdc++/113376] [14/15 Regression] " redi at gcc dot gnu.org 2024-06-12 20:40 ` redi at gcc dot gnu.org 2024-06-13 13:10 ` cvs-commit at gcc dot gnu.org 2024-07-12 10:19 ` [Bug libstdc++/113376] [14 " cvs-commit at gcc dot gnu.org 2024-07-12 10:20 ` redi 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-113376-4-akUuP0akX4@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: linkBe 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).