public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: dje@gcc.gnu.org
To: dje@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	haruki.kodera@nifty.com, nobody@gcc.gnu.org
Subject: Re: optimization/5422: powerpc -O2 -fssa -fdce misoptimization
Date: Wed, 13 Mar 2002 14:26:00 -0000	[thread overview]
Message-ID: <20020313222638.20902.qmail@sources.redhat.com> (raw)

Synopsis: powerpc -O2 -fssa -fdce misoptimization

Responsible-Changed-From-To: unassigned->dje
Responsible-Changed-By: dje
Responsible-Changed-When: Wed Mar 13 14:26:38 2002
Responsible-Changed-Why:
    powerpc
State-Changed-From-To: open->closed
State-Changed-By: dje
State-Changed-When: Wed Mar 13 14:26:38 2002
State-Changed-Why:
    @item -fssa
    @opindex fssa
    Perform optimizations in static single assignment form.  Each function's
    flow graph is translated into SSA form, optimizations are performed, and
    the flow graph is translated back from SSA form.  Users should not
    specify this option, since it is not yet ready for production use.
    
    @item -fdce
    @opindex fdce
    Perform dead-code elimination in SSA form.  Requires @option{-fssa}.  Like
    @option{-fssa}, this is an experimental feature.
    
    The SSA optimizations are experimental and should not be
    used.  The options are known to produce incorrect results.
    Until these options are supported for production use, bug
    reports cannot be addressed.  If you want to help with the
    development of these types of optimizations, please contact
    the developers directly.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5422


             reply	other threads:[~2002-03-13 22:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-13 14:26 dje [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-01-18  1:36 haruki.kodera

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=20020313222638.20902.qmail@sources.redhat.com \
    --to=dje@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=haruki.kodera@nifty.com \
    --cc=nobody@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).