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 C41543858D33; Tue, 27 Jun 2023 13:19:10 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C41543858D33
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1687871950;
	bh=6S+BEXlOdiQOuepxlcgRto2QjYGlyF0XEL1wAajkMXk=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=hbojPUprrsJN5JTBU5ohdoQNI+OsEHec7p55OfUWGUKnDQl3E/CsH4XYXIznUpSiZ
	 yNuMXMl1d2HHh2BnDC3UQN0iC2LSEBUFXrANtSS6RnCrqERrOh65aVba2k1V/8s1I9
	 49BsSOySHEU1WY6DzFwiH9VO1loAMuNhbXkd1hrw=
From: "jskumari at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/109009] Shrink Wrap missed opportunity
Date: Tue, 27 Jun 2023 13:19:10 +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: unknown
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jskumari at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jskumari at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-109009-4-za94u4HiYz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-109009-4@http.gcc.gnu.org/bugzilla/>
References: <bug-109009-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=3D109009

--- Comment #12 from Surya Kumari Jangala <jskumari at gcc dot gnu.org> ---
(In reply to Peter Bergner from comment #10)
> (In reply to Peter Bergner from comment #9)
> > Yes, you'll need to factor in the BB frequency.  Since the save/restore=
 code
> > will go into (at this point modulo shrink-wrapping later) the prologue =
and
> > epilogue, you'll want something like: <prologue/epilogue freq> * 2 *
> > "ira_memory_move_cost".
>=20
> Thinking more, depending on the allocno/mode, you might also need to fact=
or
> in calculate_saved_nregs(), in case the allocno represents a register pair
> or larger.

Yes, I am taking calculate_saved_nregs() into consideration.=