public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "xinliangli at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/46279] cmov not hoisted out of the loop
Date: Tue, 02 Nov 2010 21:33:00 -0000	[thread overview]
Message-ID: <20101102213300.V0I697yJeD8lXjBJVNEzG4OC2PxP_7BQpwoUvfhTfPs@z> (raw)
In-Reply-To: <bug-46279-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from davidxl <xinliangli at gmail dot com> 2010-11-02 21:33:37 UTC ---
Hoisting cmov out of the loop is more efficient ( I tried O3 before filing
the bug).

David

On Tue, Nov 2, 2010 at 2:31 PM, pinskia at gcc dot gnu.org <
gcc-bugzilla@gcc.gnu.org> wrote:

> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46279
>
> --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> 2010-11-02
> 21:31:03 UTC ---
> Try -O3.  -O3 enables -funswitch-loops which does this.
>
> --
> Configure bugmail: http://gcc.gnu.org/bugzilla/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug.
>


  parent reply	other threads:[~2010-11-02 21:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-02 21:28 [Bug rtl-optimization/46279] New: " davidxl at gcc dot gnu.org
2010-11-02 21:31 ` [Bug rtl-optimization/46279] " pinskia at gcc dot gnu.org
2010-11-02 21:33 ` pinskia at gcc dot gnu.org
2010-11-02 21:33 ` xinliangli at gmail dot com [this message]
2010-11-02 21:45 ` jakub at gcc dot gnu.org
2010-11-02 21:46 ` pinskia at gcc dot gnu.org
2010-11-03 10:58 ` rguenth at gcc dot gnu.org
2021-07-20  0:45 ` pinskia at gcc dot gnu.org
2022-11-11  9:32 ` tnfchris 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=20101102213300.V0I697yJeD8lXjBJVNEzG4OC2PxP_7BQpwoUvfhTfPs@z \
    --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).