public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/113376] [14/15 Regression] Confusing notes when using C++17 parallel algorithms
Date: Thu, 13 Jun 2024 13:10:34 +0000	[thread overview]
Message-ID: <bug-113376-4-C8HpZZvSJr@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 #8 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>:

https://gcc.gnu.org/g:99a1fe6c12c733fe4923a75a79d09a66ff8abcec

commit r15-1255-g99a1fe6c12c733fe4923a75a79d09a66ff8abcec
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Wed Jun 12 16:47:17 2024 +0100

    libstdc++: Fix unwanted #pragma messages from PSTL headers [PR113376]

    When we rebased the PSTL on upstream, in r14-2109-g3162ca09dbdc2e, a
    change to how _PSTL_USAGE_WARNINGS is set was missed out, but the change
    to how it's tested was included. This means that the macro is always
    defined, so testing it with #ifdef (instead of using #if to test its
    value) doesn't work as intended.

    Revert the test to use #if again, since that part of the upstream change
    was unnecessary in the first place (the macro is always defined, so
    there's no need to use #ifdef to avoid -Wundef warnings).

    libstdc++-v3/ChangeLog:

            PR libstdc++/113376
            * include/pstl/pstl_config.h: Use #if instead of #ifdef to test
            the _PSTL_USAGE_WARNINGS macro.

      parent reply	other threads:[~2024-06-13 13:10 UTC|newest]

Thread overview: 11+ 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
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 [this message]

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-C8HpZZvSJr@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).