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 81C513858D35; Fri, 16 Jun 2023 11:30:59 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 81C513858D35
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1686915059;
	bh=Y4zBVSSw04w9GBMQprdflHyzhDNiaVpUfUZHwKBAOa4=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=WlqMBwqShbXCRhI4sGROFhyYbcOizVVZJVv1pafoo+hpCj8yBLyR42hVmQ0i0oDWZ
	 fisEbJByiMTrRIYGx2nYmFkpkddo739CzaVVNReG/WDEviv79CfrRoJ3OS6mlYhxZI
	 /Tt3OKLt76zF4Cu1Nbwupr2ict4QnP/pJ72Fq384=
From: "19373742 at buaa dot edu.cn" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/110281] wrong code with '-O3'
Date: Fri, 16 Jun 2023 11:30:59 +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: 11.4.1
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: 19373742 at buaa dot edu.cn
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-110281-4-6syVPydIuK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-110281-4@http.gcc.gnu.org/bugzilla/>
References: <bug-110281-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=3D110281

--- Comment #7 from CTC <19373742 at buaa dot edu.cn> ---
(In reply to Jakub Jelinek from comment #6)
> That requires detailed analysis nobody performed yet.  csmith is known to
> generate invalid programs sometimes, especially with some options, and on=
ly
> such analysis can give definite answers.  Though, two independent compile=
rs
> behaving the same and -fno-strict-aliasing option making it go away is a
> strong indication it could very well be a bug in the generated testcase.

Thanks very much for your explanation!=