From: ami_stuff <ami_stuff@o2.pl>
To: "Paolo Bonzini" <bonzini@gnu.org>
Cc: gcc@gcc.gnu.org
Subject: Re: "-fno-unswitch-loops" option have no effect?
Date: Mon, 17 Aug 2009 16:07:00 -0000 [thread overview]
Message-ID: <30c6dc7a.7a8af09d.4a895c36.c1c89@o2.pl> (raw)
In-Reply-To: <4A895B1A.1010501@gnu.org>
Hi,
> >
> > Here are my results:
> >
> > -m68060 -O3 -fno-unswitch-loops - 12,9kb
> > -m68060 -O3 - 12,9kb
> > -m68060 -O2 -finline-functions -fgcse-after-reload -ftree-vectorize -fpredictive-commoning - 12,4kb
>
> And why do you think that loop unswitching has anything to do with the
> size growth?
Shouldn't I get the same file sizes with:
-m68060 -O3 -fno-unswitch-loops
and
-m68060 -O2 -finline-functions -fgcse-after-reload -ftree-vectorize -fpredictive-commoning
?
I don't know, but I think the same optimalizations should be used in these cases, so file size should be the same.
I'm wrong?
next prev parent reply other threads:[~2009-08-17 13:33 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
2009-08-17 13:35 ` ami_stuff
2009-08-17 16:01 ` Paolo Bonzini
2009-08-17 16:07 ` ami_stuff [this message]
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=30c6dc7a.7a8af09d.4a895c36.c1c89@o2.pl \
--to=ami_stuff@o2.pl \
--cc=bonzini@gnu.org \
--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).