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 6D5D43887F7D; Thu, 15 Dec 2022 09:01:09 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 6D5D43887F7D
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1671094869;
	bh=u4aOwgcRXaLFt53EmotPHgZrMj9OrbvBzJ1vUMRTYV0=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=vIrjKMWWLLw01kX9TK8DEHYIVxfn7Jc1nZXh0kTwPFCH80IeRWL9KOWT/8khHSiNy
	 WLdhXEQiRdwXz5ROAt4njkPVGhsWPSFtP82YFjP/9XeDJYQOmMqtKeVz6asRNB+7Nb
	 o/7jkQ+l8+s4Wk1YMWCxBRabWiZvJUwUnMJ/d1y4=
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/108117] Wrong instruction scheduling on value
 coming from abnormal SSA
Date: Thu, 15 Dec 2022 09:01:09 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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-108117-4-K0KtcPdbk6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-108117-4@http.gcc.gnu.org/bugzilla/>
References: <bug-108117-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=3D108117

--- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Feng Xue from comment #6)
> (In reply to Andrew Pinski from comment #2)
> > https://en.cppreference.com/w/c/program/setjmp
>=20
> I think that most programmers are not aware of this, neither I for sure.
> Usage of volatile here is not that intuitive as for purpose of
> multi-execution synchronization

You should read up on https://en.cppreference.com/w/cpp/utility/program/sig=
nal
too.=