public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/107772] function prologue generated even though it's only needed in an unlikely path
Date: Sun, 20 Nov 2022 19:23:35 +0000	[thread overview]
Message-ID: <bug-107772-4-Iysn5AVXFK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107772-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107772

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
           Severity|normal                      |enhancement
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2022-11-20

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Confirmed, though this is more than just the your normal shrink wrapping case
as you need to split the loop into two.

Though maybe having the prologue and epoligue around the function call instead
might be better ....

Anyways this is still a more complex case for shrink wrapping.

I Noticed that LLVM does not even do a shrink wrapping for the early return if
b == e on entering the function.

  reply	other threads:[~2022-11-20 19:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-20 18:48 [Bug rtl-optimization/107772] New: [missed optimization] " avi at scylladb dot com
2022-11-20 19:23 ` pinskia at gcc dot gnu.org [this message]
2022-11-28 18:08 ` [Bug rtl-optimization/107772] " avi at scylladb dot com
2022-11-28 18:13 ` pinskia at gcc dot gnu.org
2022-11-28 18:34 ` amonakov at gcc dot gnu.org
2022-11-28 20:32 ` avi at scylladb dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-107772-4-Iysn5AVXFK@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).