From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 8D6CA3858408; Mon, 15 Jan 2024 10:17:54 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8D6CA3858408
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1705313874;
	bh=A7zqvJUQUzAbQitPfOBLZAqoFtB9gE2dl43gjKf+ZwU=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=FSlRfAgK6wokz+GQvqG5RmiTGxoCW9yz2bSHkXeLnjE+ZYBA/mgRS43B4K0uNdXdA
	 WwdpxBmMnJuKSfhIPriH8vjxfHbJPJuoW/IJt9htcGe12X1tIuyYvBuZoCBtwRC4VZ
	 4eCg7rBoPXLbafpwOT0+Om9nxAW1i/OISpuXVTk0=
From: "redi at gcc dot gnu.org" <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 10:17:53 +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: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-113376-4-5mm7MKGFLu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-113376-4@http.gcc.gnu.org/bugzilla/>
References: <bug-113376-4@http.gcc.gnu.org/bugzilla/>
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: <gcc-bugs.sourceware.org>

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

--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Pilar Latiesa from comment #1)
> (In reply to Pilar Latiesa from comment #0)
> > I don't understand why all these functions are even instantiated as they
> > appear to be related to the vectorization of other algorithms.
>=20
> Pragma messages are shown irrespectively of whether the function is
> instantiated.

Yeah, I don't know if Clang works differently (I don't think so?) or if tho=
se
pragmas are just misused. They come from the upstream PSTL project.

>=20
> > i.e. is checking defined(_PSTL_USAGE_WARNINGS) instead of just
> > _PSTL_USAGE_WARNINGS. This logic doesn't seem right.
>=20
> This change was made as part of r14-2109-g3162ca09dbdc2e:
>=20
> - #if _PSTL_USAGE_WARNINGS
> + #if defined(_PSTL_USAGE_WARNINGS)
>=20
> I don=E2=80=99t think this change is correct.

Good catch.=