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 middle-end/108162] Missed optimization opportunity. Complex function that starts with if (param == 0) return 0;
Date: Sat, 17 Dec 2022 23:53:21 +0000	[thread overview]
Message-ID: <bug-108162-4-qm4KZ7JAzG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108162-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Levo DeLellis from comment #3)
> (In reply to Andrew Pinski from comment #2)
> > Round 4 is because of this heuriheuristics. Name the function something
> > besides main and try again.
> 
> I couldn't reproduce. fn has more than xor eax/ret. godbolt shows the same.
> x86-64 12.2 https://gcc.godbolt.org/z/WdacrE788
> 
> #include <vector>
> int fn() { std::vector<int> v; v.push_back(1000); return 0; }
> int main(int argc, char *argv[]) { fn(); }

Right that is not inlining either. Anyways there are another bugs about not
removing operator new/operator delete in some cases.

      parent reply	other threads:[~2022-12-17 23:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-17 23:01 [Bug c++/108162] New: " levo.delellis at gmail dot com
2022-12-17 23:08 ` [Bug middle-end/108162] " pinskia at gcc dot gnu.org
2022-12-17 23:13 ` pinskia at gcc dot gnu.org
2022-12-17 23:47 ` levo.delellis at gmail dot com
2022-12-17 23:53 ` pinskia at gcc dot gnu.org [this message]

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-108162-4-qm4KZ7JAzG@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).