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 03CB33851AB8; Fri, 17 Feb 2023 11:38:54 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 03CB33851AB8
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1676633935;
	bh=kZONtadPJxtZSnsUuW6/Q9GeeYbPnzjRfdnHFn0mihI=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=lBiHK/uKYh43jJAd/hBbtaVdkZ6VlHuEur2WbA7iyT4oax6R5HZjyKNLETdBUHgvm
	 W1IrTs7Id3o8L4Wuyp/Ae630CHhAydmYblVUJXgdFajPT3qbNVfrkj/OAqiClt7tzY
	 UnhuJ7BO7p9n4USQw8az84trCbrsX2rgEh/bdLVg=
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/108821] [11/12/13 Regression] LIM reissuing a
 violatile store when it cannot/should not
Date: Fri, 17 Feb 2023 11:38:53 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 11.1.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 11.4
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-108821-4-nmXk4fqzC6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-108821-4@http.gcc.gnu.org/bugzilla/>
References: <bug-108821-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=3D108821

--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>:

https://gcc.gnu.org/g:4c4f0f7acd6b96ee744ef598cbea5c7046a33654

commit r13-6114-g4c4f0f7acd6b96ee744ef598cbea5c7046a33654
Author: Richard Biener <rguenther@suse.de>
Date:   Fri Feb 17 12:36:44 2023 +0100

    tree-optimization/108821 - store motion and volatiles

    The following fixes store motion to not re-issue volatile stores
    to preserve TBAA behavior since that will result in the number
    of volatile accesses changing.

            PR tree-optimization/108821
            * tree-ssa-loop-im.cc (sm_seq_valid_bb): We can also not
            move volatile accesses.

            * gcc.dg/tree-ssa/ssa-lim-24.c: New testcase.=