From: law@redhat.com
To: Andrew Pinski <pinskia@physics.uc.edu>
Cc: gcc@gcc.gnu.org
Subject: Re: RFC: remove -fssa*
Date: Thu, 22 May 2003 17:40:00 -0000 [thread overview]
Message-ID: <200305221735.h4MHZSnf005251@speedy.slc.redhat.com> (raw)
In-Reply-To: Your message of "Thu, 22 May 2003 11:13:41 EDT." <F896FB8D-8C67-11D7-BA60-000393A6D2F2@physics.uc.edu>
In message <F896FB8D-8C67-11D7-BA60-000393A6D2F2@physics.uc.edu>, Andrew Pinski
writes:
>Since these options are going away and cause more trouble than help, I
>think they should be removed from 3.3.1 and 3.4.
>Then we can close some bugs that are because of them.
I wouldn't say they're necessarily going away -- I strongly believe that
we'll also have an RTL SSA set of optimizers in the future. But before
we have that we need to solve the mid-level RTL problem.
jeff
prev parent reply other threads:[~2003-05-22 17:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-22 15:17 Andrew Pinski
2003-05-22 17:40 ` law [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=200305221735.h4MHZSnf005251@speedy.slc.redhat.com \
--to=law@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=pinskia@physics.uc.edu \
/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).