From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id DD9F3384477A; Wed, 10 Apr 2024 17:03:20 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org DD9F3384477A DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1712768600; bh=dLAVXi9bWvSUdHeq0fEEj/MNUV96Etedai8UQlhneN8=; h=From:To:Subject:Date:In-Reply-To:References:From; b=dVYlqH/8cjvdtpo+IpVqXWtIocsR2zMQ+4BfLDI8xGd+JxEVG1hQoxFjDyU1KFpC4 xanG2NbwvZb5gcFw1ShlSzvtWlRdUMkvz1RU8bi+TgQ1utpy/HUo3aob3bc2Wid+Pk asCs2r1XY0hWxDM6yj2jyZI0Ubq4sWtlqeGNHWtI= From: "rguenth at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/101523] Huge number of combine attempts Date: Wed, 10 Apr 2024 17:03:20 +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: 12.0 X-Bugzilla-Keywords: compile-time-hog, memory-hog X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- 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=3D101523 --- Comment #59 from Richard Biener --- (In reply to Segher Boessenkool from comment #57) > (In reply to Richard Biener from comment #56) > > The fix was reverted but will be re-instantiated for GCC 15 by me. >=20 > And I still protest. >=20 > PR101523 is a very serious problem, way way way more "P1" than any of the > "my target was inconvenienced by some bad testcases failing now" "P1"s th= ere > are now. Please undo this! It was a very serious problem in 2021, too. But since we shipped with that very serious problem it is by definition not a ship-stopper. I'll also point out that your previous assessment of this bug was more as an obscure corner case. If there's a solution avoiding the code generation regressions that can be considered for backporting to GCC 14.2 or even earlier branches.=