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 1B9EF3858415; Fri,  5 Apr 2024 18:16:05 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 1B9EF3858415
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1712340965;
	bh=vjwI2PlN2Dmwkb2SYM7/kCEDqCWa0A/JvBaBRGQQwaY=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=HzFOfQNgWif3PRlKyCfncLlt2nlVPI3nSyGqiplUT71pKi6VdqykYOBCcOxnJZbyA
	 GHKDABQIyxZQN2sB9eGyVkvAT3RTAWv4d+HkMHGi4RwHqV0VbA4sp5UFspR/NlOLVC
	 mOlk1DysACUUklpjFmGTCVTFOhCp0cnexoLOOysI=
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/87299] #pragma GCC target behaves differently when
 using -save-temps
Date: Fri, 05 Apr 2024 18:16:01 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: preprocessor
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 14.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-87299-4-EPjoOXv9vL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87299-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87299-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=3D87299

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Gwenole Beauchesne from comment #8)
> Hi, can you please consider a backport to GCC 13 branch? The patch applies
> cleanly as is, but causes regressions that are further fixed with e45c564e
> (for PR pch/112319).
>=20
> GCC 13 is the first and most complete compiler for modern C++ (>=3D C++20)
> support and readily available, or soon available, as the system compiler =
for
> major distributions. This is useful to C++ projects that (debately) use
> multiple wrappers for SIMD support (xsimd, simde, mipp, etc.), but without
> correct support for runtime dispatching. So, using #pragma GCC target is a
> handy solution for that.

No, this certainly shouldn't be backported, it is a significant behavior ch=
ange
which is something that shouldn't be done on release branches.
E.g. it breaks simdutf, see https://github.com/simdutf/simdutf/issues/391=