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 374053858401; Mon, 22 Jan 2024 13:21:16 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 374053858401
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1705929676;
	bh=LeQ7eNAPoquFymfJVhRAAZ9K4JD3N0eWiyJasVClQKw=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=CpDUFMi2gqAhwKFPIL1PrLqr8FA4k5d8v04rZqzQlyPkQEd5IYZFg6vHqFu1ueih8
	 e3ZLF6bqSkIjeDX5ajnxN9hhfzrfOQaB4wtCV0xH09k4yisY2KyUoh/2RFpOYRcdMz
	 3pw2H3wfQe8I9qX6HClXie2zVOJzO5yiXeWV3goQ=
From: "juzhe.zhong at rivai dot ai" <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: Mon, 22 Jan 2024 13:21:15 +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: 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: <bug-113495-4-QyJodWxh2N@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

--- Comment #30 from JuzheZhong <juzhe.zhong at rivai dot ai> ---
Ok. I believe m_avl_def_in && m_avl_def_out can be removed with a better
algorthm.

Then the memory-hog should be fixed soon.

I am gonna rewrite avl_vl_unmodified_between_p and trigger full coverage
testingl
Since it's going to be a big change there.=