From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 8DFDE3858C62; Wed, 24 Jan 2024 12:48:45 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8DFDE3858C62 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1706100525; bh=iDGHuCWyMX0gt72Tz6XXh9y/5eq7yMXp+/4otSm4kPE=; h=From:To:Subject:Date:In-Reply-To:References:From; b=KPpxr5IBNQJrDtFTCFWumalt0jOD97/W9lIGM7nF0X1QQzL0f5OxE8xBusfyfyJbt fDVnknof1bQueQK5taSpyn21sgJCZLDRbXRiGFpbgbO1RCy1SNWRtX8fbHYElq+Ot+ Zyr2N7dr35faX6U+liQiv2fHOS9Z3xVHD+EC3C/k= From: "rearnsha at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/113542] gcc.target/arm/bics_3.c regression after change for pr111267 Date: Wed, 24 Jan 2024 12:48:44 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: rtl-optimization X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: testsuite-fail X-Bugzilla-Severity: normal X-Bugzilla-Who: rearnsha at gcc dot gnu.org X-Bugzilla-Status: NEW 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: everconfirmed bug_status cf_reconfirmed_on 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=3D113542 Richard Earnshaw changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Last reconfirmed| |2024-01-24 --- Comment #1 from Richard Earnshaw --- Options to reproduce -O2 -mcpu=3Dcortex-m3 -mthumb The problem is really a back-end issue. But the cause is that the fwprop p= ass is now merging propagating insn 9 into insn 10, replacing: (set (reg:SI 124 [ _7 ]) (ne:SI (reg:CC 100 cc) (const_int 0 [0]))) with the flag setting instruction to form (parallel [ (set (reg:SI 124 [ _7 ]) (ne:SI (reg:SI 122 [ _2 ]) (const_int 0 [0]))) (clobber (reg:CC 100 cc)) ]) That's OK, but it means that the combine pass is no-longer able to merge the flag setter with an earlier result producer. A similar thing starts to happen arm state this is dropped because the costs are working out as the same (it has to reduce the cost). So I think it's that the cost model for thumb2 needs tweaking.=