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 78483384BC09; Thu,  6 Oct 2022 19:04:46 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 78483384BC09
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1665083086;
	bh=COX0QDYo3wMUbefOSrXHUHbUxsO9m0sHl9BKTdx9Q1w=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=R/K3NnrE3yIBu6SJnxcl0Z4A3glRq2UId8lhh5rHLt233oucn6HVCvgT/PmodN/42
	 VbeRxhsRWunFfXWQNc4od/aJuvbPuxy8SLaG/naWAdgD7RbDLf1TGFJy6lWALCjICd
	 4DQIWz65MK8RPJHdq0ccVLX/zyVS0Ubk5d9qa3xs=
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/107115] Wrong codegen from TBAA under stores that
 change effective type?
Date: Thu, 06 Oct 2022 19:04:46 +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: 13.0
X-Bugzilla-Keywords: alias, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
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-107115-4-sDVHzWqLd6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-107115-4@http.gcc.gnu.org/bugzilla/>
References: <bug-107115-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=3D107115

--- Comment #9 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Alexander Monakov from comment #8)=20
> We need a solution that works for combine too =E2=80=94 is it possible to=
 invent a
> representation for a no-op in-place MEM "move" that only changes its alias
> set?

That is the same as my comment here:
> I don't know what is the best way to represent an aliasing set change
> even though the value didn't change on the RTL level.

Clobber might work though I don't know if that is 100% correct as the value
didn't change so maybe a new RTL code for this? But that would require many
changes in the backend ...=