From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 4CFEF388211C; Thu, 13 Jun 2024 13:10:35 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4CFEF388211C DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1718284235; bh=JHyF09+9op4G09B91FmF6aHFzMR0MaTnsKMncTriTkM=; h=From:To:Subject:Date:In-Reply-To:References:From; b=g1NxUaWn1CpUWjuxcAXERH5KlHLVtRBBlqukiv42ddi4oWvYc5algsERCh1HBNdKV DigGnwPjwlSzCB8CPo1Af+iGt9vz402tJWnRlcBn5+iSXaLLyslXN49nixCwOwnJ+d SxcEY84wPSOOF/qmBYQfCIj1IfcAZAM2sncSCBZA= From: "cvs-commit at gcc dot 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: patch X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: redi at gcc dot gnu.org X-Bugzilla-Target-Milestone: 14.2 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D113376 --- Comment #8 from GCC Commits --- The master branch has been updated by Jonathan Wakely : https://gcc.gnu.org/g:99a1fe6c12c733fe4923a75a79d09a66ff8abcec commit r15-1255-g99a1fe6c12c733fe4923a75a79d09a66ff8abcec Author: Jonathan Wakely 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.=