From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 4341C385C6EE; Fri, 8 Mar 2024 15:05:44 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4341C385C6EE DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1709910344; bh=mpQmuIDwhFwDia6M/Fcg7fC5yEDuuMH1CqC3ubJ/BxI=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Cs9MRs6cfR/FLNRgdw12ww6b0Jv+i3zQiyFzN/73c4kOkjfTXpvy7CGtICyTPUVvZ KcwE56d/BQqOkGYAFgz8VtuKKN/EGRxB3xYA0SQkRe0ORByD9/X3XOCt6yd1YLpRsp BIu5oayr4KUvnX8plEoNerC90P75Y6De2DEs2XOE= From: "jakub at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/114284] [14 Regression] arm: Load of volatile short gets miscompiled (loaded twice) since r14-8319 Date: Fri, 08 Mar 2024 15:05:43 +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: 14.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: jakub at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 14.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D114284 --- Comment #5 from Jakub Jelinek --- (In reply to Alex Coplan from comment #3) > I think this has been fixed by > r14-9379-ga0e945888d973fc1a4a9d2944aa7e96d2a4d7581 Maybe the volatile MEM case yes, but I don't see how it would avoid the undesirable MEM propagation when it is used multiple times, across EBBs or = into paradoxical subregs.=