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 414FB3858D1E; Sat,  1 Oct 2022 02:25:13 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 414FB3858D1E
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1664591113;
	bh=dQWl5NS4YMfNyNNYNpHhrFq1r5TuMH2tBBmbAs2pBjU=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=bqQLa7JApAFrwzcjTOWFioGcCk2PQXy9DgfHFYcqoDkDEmptmUh97YjcZqwcwpNpF
	 dFPoejp36W0SW5Nng3bbWBntS7WSWIHOlkO3KeOHb7hTac2NBH0pWn+/XONsv/zwKe
	 TGfryD/zQ4UJXjtukKtSRwUsjjEYO5hQk3nZf5So=
From: "bugdal at aerifal dot cx" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/107107] Wrong codegen from TBAA when stores to
 distinct same-mode types are collapsed?
Date: Sat, 01 Oct 2022 02:25:11 +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: unknown
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bugdal at aerifal dot cx
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-107107-4-D0CrTcLQxs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-107107-4@http.gcc.gnu.org/bugzilla/>
References: <bug-107107-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=3D107107

--- Comment #1 from Rich Felker <bugdal at aerifal dot cx> ---
There's also a potentially related test case at https://godbolt.org/z/jfv1G=
e6v4
- I'm not yet clear on whether it's likely to have the same root cause.=