From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 2BBE93858D38; Thu, 28 Sep 2023 06:48:03 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2BBE93858D38 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1695883683; bh=d8ZRgK7hq0TzqMs0Bg+n6E/sw2mlFwz48D3kR8AAAxs=; h=From:To:Subject:Date:In-Reply-To:References:From; b=tRmTZxhyXbCYhPgxj24NHavczI8P3siGsiNOzS9Vr2OYDwqy/EJ1IkdsUv+/TBqfM rM/I/7/0RuH3pO0Jknlp6yWlUArPLGZ80P3v7mM5JjeEznieUJdDqsoSMP9Ae6H1DI usrrgz/Bx5+Kg+ziBQg/RUYwObmJwVvVOX2N4wkE= From: "rguenth at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/111619] [14 regression] 'make profiledbootstrap' makes 10+ minutes on insn-recog.cc (x86_64-linux) Date: Thu, 28 Sep 2023 06:48:02 +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: compile-time-hog X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 14.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cf_gcctarget target_milestone 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=3D111619 Richard Biener changed: What |Removed |Added ---------------------------------------------------------------------------- Target| |x86_64-*-* Target Milestone|--- |14.0 --- Comment #10 from Richard Biener --- PRE : 444.33 ( 55%) 0.19 ( 4%) 444.86 ( = 54%) 216k ( 0%) There's a few other bugs about RTL PRE being slow (it's usually the dataflow parts implemented with big sbitmaps and expression hashes). I've tried a few times to get my hands into that but it's somewhat difficult. For profile-generate we have a lot more memory ops which is what likely kills us here (lots of bitmap iteration with disabled inlining/optimization= ). Is this really a regression in GCC 14? Note we are already using -fno-checking for building stage2.=