From: Steven Bosscher <stevenb@suse.de>
To: gcc@gcc.gnu.org
Cc: Kazu Hirata <kazu@cs.umass.edu>, sam124@operamail.com
Subject: Re: Useless assembly
Date: Sun, 28 Nov 2004 22:06:00 -0000 [thread overview]
Message-ID: <200411282242.37120.stevenb@suse.de> (raw)
In-Reply-To: <20041128.163544.55510006.kazu@cs.umass.edu>
On Sunday 28 November 2004 22:35, Kazu Hirata wrote:
> Hi Sam,
>
> > Optimizing it at -O3 (which I'm sure includes SSA, DCE, and CCP)
> > just made the compilation take longer and generate more assembly
> > then the first time.
>
> -O3 does not enable SSA-based optimizations.
In fact with GCC 3.4.3, nothing enables SSA-based optimizations.
How could it, there are none.
Gr.
Steven
next prev parent reply other threads:[~2004-11-28 21:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-28 21:40 Sam Lauber
2004-11-28 21:41 ` Kazu Hirata
2004-11-28 21:56 ` Eric Botcazou
2004-11-28 22:06 ` Steven Bosscher [this message]
2004-11-28 22:46 ` jlh
2004-11-29 4:25 ` Robert Dewar
2004-11-29 12:04 ` Andreas Schwab
2004-11-30 3:12 Sam Lauber
2004-11-30 4:36 ` Robert Dewar
2004-11-30 14:12 ` Dave Korn
2004-11-30 16:20 ` Robert Dewar
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=200411282242.37120.stevenb@suse.de \
--to=stevenb@suse.de \
--cc=gcc@gcc.gnu.org \
--cc=kazu@cs.umass.edu \
--cc=sam124@operamail.com \
/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).