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 EC6293858D39; Wed, 29 Mar 2023 07:36:10 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org EC6293858D39
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1680075370;
	bh=pxDp7yCSDWzDz3xAyDTEbSziq3IOEuFSlIejSfcdvWA=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=VsEZTVCYI0xBXIfu4wNAqNhh5Und7wNFioMnmf+Dmd5Z97/yOaGXBirjFdo7MH98A
	 tmbE4OE4Z3XgioF1j7G0wz4GU2Q1fu4viTbhoS+hIe+scsU9Z13zSobNjIZjR008Sm
	 Y+eY5uOfe8fjR7+a6KiY3v8/GnFMZrKoSyx8NQ5M=
From: "xry111 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/108357] [13 Regression] Dead Code Elimination
 Regression at -O2 since r13-4607-g2dc5d6b1e7ec88
Date: Wed, 29 Mar 2023 07:36:10 +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: 13.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: xry111 at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 13.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-108357-4-0wHNdsIJ5a@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-108357-4@http.gcc.gnu.org/bugzilla/>
References: <bug-108357-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=3D108357

--- Comment #7 from Xi Ruoyao <xry111 at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #6)
> (In reply to Xi Ruoyao from comment #5)
> > The test fails on loongarch64-linux-gnu.  foo is kept in 114t.threadful=
l1,
> > but removed in 135t.forwprop3.
> >=20
> > Does this mean something is wrong for LoongArch, or we should simply ch=
eck
> > the tree dump in a later pass (for e.g. 254t.optimized)?
>=20
> I guess it depends on LOGICAL_OP_NON_SHORT_CIRCUIT, can you try
> --param logical-op-non-short-circuit=3D1 and see if that helps?

Nope, the result is same.=