From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 017EC385842A; Fri, 23 Jun 2023 20:04:55 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 017EC385842A DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1687550696; bh=UUQX172Z4Igq8SWIXA1mRYPPvYvZANasPQukNbOLLTA=; h=From:To:Subject:Date:In-Reply-To:References:From; b=gvfVQsuks+GIYpDU4Sep3KOIUx/WrL+Kjt1BgBzvl1b6b8WTJl0vcWB5B1Py5iETz 7farnKNhxrl3ni2eDrQtp8irFCxLBhkYeci7iBl8Ibv0VRJBtwW8azIy8ySfSlonBu KYIQj5FnhBW1mpSbgnZKyLMBXs2Cp3BhNdST5AQI= From: "bergner at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/109009] Shrink Wrap missed opportunity Date: Fri, 23 Jun 2023 20:04:55 +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: bergner 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: 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=3D109009 --- Comment #10 from Peter Bergner --- (In reply to Peter Bergner from comment #9) > Yes, you'll need to factor in the BB frequency. Since the save/restore c= ode > will go into (at this point modulo shrink-wrapping later) the prologue and > epilogue, you'll want something like: * 2 * > "ira_memory_move_cost". Thinking more, depending on the allocno/mode, you might also need to factor= in calculate_saved_nregs(), in case the allocno represents a register pair or larger.=