From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 9151A3858D1E; Fri, 19 Jan 2024 01:52:07 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9151A3858D1E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1705629127; bh=EiylTBIdWjqfhxX+vDTmEOSFOfHD1r9ASjePdxHgtUI=; h=From:To:Subject:Date:In-Reply-To:References:From; b=iw4372iQt8lWlBXkzwemlg/1KFoyF81bxhQpKgrFCuz3VCc74DJZPZfpGFGmvoOLm 4eG+oRRl/it3hGabqqBa+GFTbIQbPTyrOVEY3v1PTsNlIwJTaUZA9fdz034GvrVPp5 fpP7TP0UYtgo3luhwnQSHZhTipY9M9Fz2pYmufbU= From: "juzhe.zhong at rivai dot ai" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/113495] RISC-V: Time and memory awful consumption of SPEC2017 wrf benchmark Date: Fri, 19 Jan 2024 01:52:07 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: compile-time-hog, memory-hog 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: --- 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=3D113495 --- Comment #4 from JuzheZhong --- Also, the original file with -fno-move-loop-invariants reduce compile time = from 60 minutes into 7 minutes: real 7m12.528s user 6m55.214s sys 0m17.147s machine dep reorg : 75.93 ( 18%) 14.23 ( 88%) 90.15 ( 2= 1%) 33383M ( 95% The memory report is quite obvious (consume 95% memory). So, I believe VSETVL PASS is not the main reason of compile-time-hog, it should be loop invariant PASS. But VSETVL PASS is main reason of memory-hog. I am not familiar with loop invariant pass. Can anyone help to debug compile-time hog of loop invariant PASS. Or should we disable loop invariant pass by def= ault for RISC-V ?=