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/31889] compiler misses opportunity to combine multiple identical function return paths
Date: Sat, 24 Jul 2021 22:17:13 +0000	[thread overview]
Message-ID: <bug-31889-4-aGx2hMiD3R@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-31889-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #4)
>         jg      .L2             # Shouldn't these two just
>         jge     .L6             # be one "je .L6"?
> 
> Is fixed with:
> 2007-06-12  Richard Guenther  <rguenther@suse.de>
> 
>         PR tree-optimization/15353
>         PR tree-optimization/31657
>         * passes.c (init_optimization_passes): Add pass_tree_ifcombine.
>         * timevar.def: Add TV_TREE_IFCOMBINE.
> 
> The other parts are confirmed.

Except it is no longer fixed by that.  That broke in GCC 10.

  parent reply	other threads:[~2021-07-24 22:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-31889-4@http.gcc.gnu.org/bugzilla/>
2012-01-28  2:25 ` pinskia at gcc dot gnu.org
2021-07-24 22:17 ` pinskia at gcc dot gnu.org [this message]
2023-09-03  3:44 ` pinskia at gcc dot gnu.org
2007-05-10  5:04 [Bug rtl-optimization/31889] New: " raeburn at raeburn dot org
2007-05-10  5:04 ` [Bug rtl-optimization/31889] " raeburn at raeburn dot org
2007-05-10  6:13 ` steven at gcc dot gnu dot org
2007-05-10 21:25 ` raeburn at raeburn dot org

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-31889-4-aGx2hMiD3R@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).