From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 3959D3858428; Wed, 10 Apr 2024 15:57:15 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3959D3858428 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1712764635; bh=1vvGT+LADo/JOPhvZl0/Wio9cHasZAeeIdesLKUPErE=; h=From:To:Subject:Date:In-Reply-To:References:From; b=hdpMmZG5VHXaHxEJOyNqVra+kNrhO7M4ONlDFLh/s85Bp37xfFCmwLvT0lNoUXTz4 c9mO2MPhO8rbVnNW/TT7ghRpNZiKrQ58wfaWxj5cB+GU5ojEWgvi0ShTHtcAoGYx0f ByqcJHBcvSsnrR7SgGGxtlZHaNUrz2gkRwqYNb9s= From: "jakub 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 15:57:14 +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: jakub 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 #58 from Jakub Jelinek --- (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 isn't just the case where some unimportant testcase would need to be xfailed, there are 5% slowdowns on SPEC and similar bugs as well. Yes, PR101523 is important to get fixed, but we've lived with it for years = and don't have time in GCC 14 cycle to deal with the fallouts from the change, which there are clearly many. If the fix was done in stage1, there could be time to deal with that, but we want to release in 2 weeks or so.=