From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id CB4393858C62; Fri, 19 Jan 2024 03:56:06 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org CB4393858C62 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1705636566; bh=o2UP5tYyv7GHdYOq0b0cz0a2kgIpjE0rDANUmCUFwTo=; h=From:To:Subject:Date:In-Reply-To:References:From; b=crXkUgOcYH4NjLgtuLJzqU7ec3/vCbHz5mIpajujk8sIG7GWX+gAJTi/beh4aUSBp L1nqe4vOTwvb6/GqmKTwF0CyVJVIPFsBE8nWGj8WTPWhUKkhVxxy+iiAy6c7ttbiZV Z5V97n29QUw1O4BaJyk6CUxG4hpMKHT8oVQOlwZo= From: "pinskia at gcc dot 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:56:05 +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: pinskia 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: --- 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 #15 from Andrew Pinski --- (In reply to JuzheZhong from comment #14) > Oh. I known the reason now. >=20 > The issue is not RISC-V backend VSETVL PASS. >=20 > It's memory bug of rtx_equal_p I think. It is not rtx_equal_p but rather RVV_VLMAX which is defined as: riscv-protos.h:#define RVV_VLMAX gen_rtx_REG (Pmode, X0_REGNUM) Seems like you could cache that somewhere ...=