public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "carrot at google dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/41004] missed merge of basic blocks
Date: Wed, 19 Aug 2009 21:55:00 -0000	[thread overview]
Message-ID: <20090819215540.13739.qmail@sourceware.org> (raw)
In-Reply-To: <bug-41004-17659@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from carrot at google dot com  2009-08-19 21:55 -------
(In reply to comment #2)
> Why does the basic block reordering pass also not handle this?
> 

Basic block reordering is disabled with options -Os. 

The basic block reordering algorithm is for performance only, it usually
increases code size. So it won't be called when do optimization for size. But
for this specific case, the extra branch can be removed when I compile it with
-O2.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41004


  parent reply	other threads:[~2009-08-19 21:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-08  0:10 [Bug target/41004] New: " carrot at google dot com
2009-08-08  0:10 ` [Bug target/41004] " carrot at google dot com
2009-08-08  9:07 ` steven at gcc dot gnu dot org
2009-08-08 10:07 ` [Bug middle-end/41004] " steven at gcc dot gnu dot org
2009-08-08 10:36 ` rguenth at gcc dot gnu dot org
2009-08-19 21:55 ` carrot at google dot com [this message]
2009-08-19 23:07 ` rth at gcc dot gnu dot org
2010-01-11  9:36 ` steven at gcc dot gnu dot org
     [not found] <bug-41004-4@http.gcc.gnu.org/bugzilla/>
2012-02-04  3:01 ` pinskia at gcc dot gnu.org
2012-03-17  0:02 ` steven at gcc dot gnu.org
2012-11-08 23:07 ` steven at gcc dot gnu.org
2012-11-09 21:38 ` steven at gcc dot gnu.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=20090819215540.13739.qmail@sourceware.org \
    --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).