public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Guenther <richard.guenther@gmail.com>
To: ami_stuff <ami_stuff@o2.pl>
Cc: gcc@gcc.gnu.org
Subject: Re: "-fno-unswitch-loops" option have no effect?
Date: Mon, 17 Aug 2009 13:33:00 -0000	[thread overview]
Message-ID: <84fc9c000908170438t787f3e75w15c44dd8e9080a2d@mail.gmail.com> (raw)
In-Reply-To: <5dd91bc1.7ff0289a.4a88a6a0.1e15f@o2.pl>

On Mon, Aug 17, 2009 at 2:38 AM, ami_stuff<ami_stuff@o2.pl> wrote:
> Hi,
>
> I found out that when I use "-fno-unswitch-loops" option, it have no effect - loops are unswitched anyway:
>
> -O3 -fno-unswitch-loops
>
> Because of that to avoid -funswitch-loops optimization I must use something like this:
>
> -O2 -finline-functions -fpredictive-commoning -fgcse-after-reload -ftree-vectorize
>
> Is that a bug?

Works fine for me.  gcc.dg/tree-ssa/loop-6.c is unswitched with -O3
but not with -O3 -fno-unswitch-loops.

You have to be more specific.  Maybe PRE or if-conversion perform
the "unswichting" for you.

Richard.

> Tested with GCC 4.4.1 (m68k).
>
> Regards
>
>

  parent reply	other threads:[~2009-08-17 11:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-17  7:19 ami_stuff
     [not found] ` <56d259a00908170344v54442954u3a5d0337de3b98fe@mail.gmail.com>
2009-08-17 13:29   ` ami_stuff
2009-08-17 19:42     ` Bernd Roesch
2009-08-17 19:54       ` ami_stuff
2009-08-17 22:16       ` Alexander Strange
2009-08-17 13:33 ` Richard Guenther [this message]
2009-08-17 13:35   ` ami_stuff
2009-08-17 16:01     ` Paolo Bonzini
2009-08-17 16:07       ` ami_stuff
2009-08-17 16:14         ` Paolo Bonzini

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=84fc9c000908170438t787f3e75w15c44dd8e9080a2d@mail.gmail.com \
    --to=richard.guenther@gmail.com \
    --cc=ami_stuff@o2.pl \
    --cc=gcc@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).