From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id CC82E3858C54; Thu, 13 Apr 2023 13:05:07 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org CC82E3858C54 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1681391107; bh=Kz62e9Nf4A0JDrfxadYr7wQTx7ARtMl6ZbxefVTuhnY=; h=From:To:Subject:Date:In-Reply-To:References:From; b=ApujclkFHo53HINJRjpbttJm4k+4EAkn3/6DH07UV8J2IbK6iog2XUFeh/LoryJwZ 6anfBboExJ/EXYSpdhJx8Wtxq3Y9OxCwYoiI6Ub60RCZU853Lpbm/qxMJT3/Ei+cEC XsbqHRtarFtdu6NSC2spHlQhgT1GHgmJdYVkz/ww= From: "rguenther at suse dot de" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/108357] [13 Regression] Dead Code Elimination Regression at -O2 since r13-4607-g2dc5d6b1e7ec88 Date: Thu, 13 Apr 2023 13:05:07 +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: rguenther at suse dot de 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: In-Reply-To: References: 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: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D108357 --- Comment #13 from rguenther at suse dot de --- On Thu, 13 Apr 2023, chenglulu at loongson dot cn wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D108357 >=20 > --- Comment #10 from chenglulu --- > (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 > If the definition of the macro DEFAULT_SIGNED_CHAR is changed to 0, the t= est > case can pass the test. I guess it is because the definition of > DEFAULT_SIGNED_CHAR affects the optimization of the ccp pass, resulting i= n some > blocks that cannot be removed, resulting in the failure of this test case. Can you check if making b unsigned fixes the test for you? If so that's what we should do.=