From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id E992F3858C62; Fri, 19 Jan 2024 03:08:26 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E992F3858C62
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1705633706;
	bh=bSqOINMlMtpCOljovgEdZyTq1idvfLBDuiRT2chUS30=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=xfmCKEm7nPO+GVGsohFlVHpIDsetyUC78hor41RAqXj1RlirVGCjDEY7ghiN4kp67
	 KxmmxWT50zfaxMtcwLYRk1R4J3QsnhSeNMgN7m71XLFbUSQe79R2ThrlpnVnMXKBmQ
	 q2IGZrOaVzE+l+uS81oDAcqWimAMEyXNOIatKSGM=
From: "patrick at rivosinc dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/113495] RISC-V: Time and memory awful
 consumption of SPEC2017 wrf benchmark
Date: Fri, 19 Jan 2024 03:08:24 +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, memory-hog
X-Bugzilla-Severity: normal
X-Bugzilla-Who: patrick at rivosinc dot com
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: cc
Message-ID: <bug-113495-4-cvU16ILTmG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-113495-4@http.gcc.gnu.org/bugzilla/>
References: <bug-113495-4@http.gcc.gnu.org/bugzilla/>
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: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D113495

Patrick O'Neill <patrick at rivosinc dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |patrick at rivosinc dot com

--- Comment #7 from Patrick O'Neill <patrick at rivosinc dot com> ---
I believe the memory hog is caused by this:
https://gcc.gnu.org/git/?p=3Dgcc.git;a=3Dblob;f=3Dgcc/config/riscv/riscv-vs=
etvl.cc;h=3D2067073185f8c0f398908b164a99b592948e6d2d;hb=3D565935f93a7da629d=
a89b05812a3e8c43287598f#l2427

In the slightly reduced test program I was using to debug there were ~35k b=
b's
leading to num_expr being roughly 1 million. vsetvl then makes 35k bitmaps =
of
~1 million bits.=