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 E5D473851ABD; Fri, 24 Mar 2023 22:17:32 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E5D473851ABD
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1679696252;
	bh=Njv0wmH58H+ZTaCQDKbWd+6fpo+r3YGuVYAoxJ++OWQ=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=XqAFFp2egDByzV+uS6+2T/4bvEX1ez4kH5TAAPDgWU+KRIOzUDWKnULnaXvRW0RFG
	 5Fgko0krS7ZTbfEd6XrHjthwPF1B8dLH37YofSckYIxeIK623jx4k0WIY8H2didOpQ
	 dScVFDw+gL4H90NPfxfoTNgGRDQgYnFtc1/pi/DI=
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/109279] [13 Regression] RISC-V: complex constants
 synthesized vs. fetching from constant pool
Date: Fri, 24 Mar 2023 22:17:32 +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: unknown
X-Bugzilla-Keywords: 
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: <bug-109279-4-xLJO8TwKFi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-109279-4@http.gcc.gnu.org/bugzilla/>
References: <bug-109279-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=3D109279

--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Vineet Gupta from comment #4)
> But this is not so much about code bloat, we see 3.5% additional dynamic
> icount on qemu which will affect perf even if we didn't care about code s=
ize
> at all.

Again dynamic icount increase does not always equals worse performance;
especially when it comes to loading from memory. It is a much more complex
equation depending on the cache and such.
Now we should be able to form these constants better in the first place too=
.=