From: Cyrille Chepelov <cyrille@chepelov.org>
To: gcc@gcc.gnu.org
Subject: Re: empty loop elimination (lack of) ?
Date: Sun, 10 Feb 2002 12:26:00 -0000 [thread overview]
Message-ID: <20020210202253.GA19630@calixo.net> (raw)
In-Reply-To: <88AEA72F-1435-11D6-AA16-000393122612@physics.uc.edu>
> I did not see the results you got.
> I even don't get a List<int>::isValid() const
OK, it took me some time to investigate, and even more to report something
meaningful out of the brute force results I've produced.
At first, I noticed that you had -funroll-loops in your command line; I had
mentioned that -funroll-loops gives the result I'm looking for (elimination
of the loop and inlinage of the resulting function), but I don't always want
to unroll loops, merely eliminating empty loops would be enough for me.
So, I tried a brute force solution: I've tried all combinations of 1, 2, 3,
4 and 5 arguments picked in the whole list of arguments in your command
line, in addition to -O3 -Wall. The results are at
http://www.chepelov.org/cyrille/loop-destroy/ (warning, lots of .s files)
matches.log contains all the "good" command lines
It looks like the following arguments are winners (they appear in every line
in the previously mentioned matches.log file):
--param max-inline-insns=10000 -save-temps
Would that be sane defaults for, say, -O3, or do these arguments carry
unwanted behaviour ?
-- Cyrille
--
Grumpf.
prev parent reply other threads:[~2002-02-10 20:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-28 14:59 Cyrille Chepelov
2002-01-28 15:37 ` Andrew Pinski
2002-02-10 12:26 ` Cyrille Chepelov [this message]
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=20020210202253.GA19630@calixo.net \
--to=cyrille@chepelov.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).