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 2EEC9384AB55; Mon, 22 Apr 2024 09:37:19 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2EEC9384AB55
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1713778639;
	bh=0wr254kMbP7tnAvsOHK7MszXrky+pPWhIdJ8bTjtpvQ=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=qPNsEEU89zKaXu5Q/O61CNuR2MviFMUJJkUMEWycPax5JT8Ver95V0se68WRvHkYH
	 Zet4y8+ttsZW0OhRlZGcmg6SUf0Va133jAScvXOTy0odmlS/nmqa3wpBfAipWA0TR0
	 pKzaGh2VSQQj9KeSF3wyoSSpwBM0k6yaMj3TdDK0=
From: "krebbel at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/114676] [12/13/14 Regression] DSE removes assignment
 that is used later
Date: Mon, 22 Apr 2024 09:37:11 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 12.1.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: krebbel at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 12.4
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-114676-4-srwEad2qny@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-114676-4@http.gcc.gnu.org/bugzilla/>
References: <bug-114676-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=3D114676

--- Comment #16 from Andreas Krebbel <krebbel at gcc dot gnu.org> ---
(In reply to Aleksei Nikiforov from comment #15)
> I think fixing compiled code should be possible. I'm not sure if this bug
> should be just closed.

In addition to fixing the PyTorch usage of the builtin, I also plan to chan=
ge
GCC to the "alias everything" approach now. Although the documentation does=
 not
strictly requires us to, it prevents other users from falling into the same
trap and makes GCC to match what Clang already does. The documentation anyw=
ay
discourages everyone from using these builtins. So it should not be a big d=
eal,
if we sacrifice a bit of performance to make it more robust.=