From: Diego Novillo <dnovillo@redhat.com>
To: Andreas Jaeger <aj@suse.de>
Cc: gcc@gcc.gnu.org
Subject: Re: Usable flags for tree-ssa-branch?
Date: Tue, 15 Oct 2002 06:11:00 -0000 [thread overview]
Message-ID: <20021015111002.GB23222@tornado.toronto.redhat.com> (raw)
In-Reply-To: <ho7kgkp44z.fsf@gee.suse.de>
On Tue, 15 Oct 2002, Andreas Jaeger wrote:
> I noticed today that -ftree-ssa has been removed and -ftree-ccp is
> used by Diego. I will use that one also on my SPEC tester. What is
> the status of other flags that are usable? Should I add some more?
>
Right now -O2 enables tree-ssa. What it does is trigger the main
analysis passes: flowgraph, data reference finder and SSA. Each
optimization pass needs to be enabled with a different -ftree-XXX
switch (invoke.texi documents the different -ftree passes).
The only pass that is close to working right now is CCP. The
idea is for passes to be enabled at -O2 as we start fixing them.
If you want to enable passes with -ftree-XXX, that's great. The
safest way, however, is to use -O2.
Diego.
prev parent reply other threads:[~2002-10-15 11:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-15 2:11 Andreas Jaeger
2002-10-15 6:11 ` Diego Novillo [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=20021015111002.GB23222@tornado.toronto.redhat.com \
--to=dnovillo@redhat.com \
--cc=aj@suse.de \
--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).