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 E42693858D28; Tue, 22 Aug 2023 07:51:33 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E42693858D28
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1692690693;
	bh=7oYmxnB3xwKdpQ/5HcLQAQuoyh54FL+KuXnt/ZiEYuE=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=G7RHepmwPj5S9PLWt8zsktjYfV3f+Qxih344Sn/w57keCwpxUszn4W4OGM4Tw0Zsb
	 qJuF2+IDUbLMoJ2cEK4Hb+8NovejMmx9onO43X+BA4WSfHaZSTy+Uaq96h2+D/flbo
	 WxREZs1R9yPja91ZaAoSx5QseBL8M90JEih7vGrU=
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/111097] mistifying bug triggered by trivial code change
Date: Tue, 22 Aug 2023 07:51:33 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 13.2.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
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-111097-4-pbjP11aIK8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-111097-4@http.gcc.gnu.org/bugzilla/>
References: <bug-111097-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=3D111097

--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
> Worth noting, this code works correctly with Visual Studio and with clang.

Gcc is known to be take more into account when it comes to aliasing rules o=
f c
and c++. That is exactly what you are running into really.=