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 5FCBA3854801; Fri, 21 Jul 2023 08:33:10 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5FCBA3854801
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1689928390;
	bh=xso2W52nby1V6cZEE1zWkQwyWQFaQd94sxV0rbDznwU=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=uOqmmPxAC2rrj5ZemRosKSZNFv5u2XOogXSlTuQxkzBmTzti5FqaTrmZjgZIY30A6
	 Rq4zKvDshoSZnfpooo1PBr58LhbrBZBHuhAwwa74P7eIvujrhBmcnD8fhqcMrTsBhq
	 3Q9XYFYvCPeCjp/3hrcIBCOQy44GZr4VgWo6HGpA=
From: "muecker at gwdg dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/110754] assume create spurious load for volatile
 variable
Date: Fri, 21 Jul 2023 08:33:10 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 14.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: muecker at gwdg dot de
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-110754-4-xSPsHZQFPK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-110754-4@http.gcc.gnu.org/bugzilla/>
References: <bug-110754-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=3D110754

--- Comment #6 from Martin Uecker <muecker at gwdg dot de> ---

One should check whether there is a similar issue with atomics, at least
regarding accidentally introducing memory ordering or so.=