From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id AECC83857C41; Fri, 13 Oct 2023 01:39:21 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org AECC83857C41 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1697161161; bh=vA8y2gBnjKxM97nLMR5XwHLxV1Hsbixmiq4O2W3642I=; h=From:To:Subject:Date:In-Reply-To:References:From; b=uB4Meu0UPCV1kuhP1UJCd54bxYCeIBG9tzhrn2Li6LnnPVKJO2TJshMWHd7QD+Zo8 oJdhs8ODnfivrDBYRMO+AjbHXyjyhH+Ew4zOo/Xaowi09L8rmWXnICgyz9OVUyuwTz mncgUjc7oQJczXoU1SPzpSMN34UZ3zXMulAEhvgc= From: "juzhe.zhong at rivai dot ai" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/111600] [14 Regression] RISC-V bootstrap time regression Date: Fri, 13 Oct 2023 01:39:21 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: compile-time-hog, needs-bisection X-Bugzilla-Severity: normal X-Bugzilla-Who: juzhe.zhong at rivai dot ai 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: cc 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=3D111600 JuzheZhong changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |juzhe.zhong at rivai dot ai --- Comment #24 from JuzheZhong --- (In reply to Robin Dapp from comment #23) > For the lack of a better idea (and time constraints as looking for compil= er > bottlenecks is slow and tedious) I went with Kito's suggestion of splitti= ng > insn-emit.cc >=20 > This reduces this part of the compilation with eight threads to 40s (from= 10 > min before). I evenly split the number of patterns into the 10 files but= it > just so happens that the last file will receive all the problematical > maybe_code_for functions, so that file makes up for most of the 40s. The > rest usually takes 5-20s. >=20 > Doing bootstrapping tests now, going to post an initial patch once it's > "presentable". Hi, Robin. I believe your patch can solve the compile-time issue. But I wonder whether it can fix memory consumption too ?=