public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Giovanni Bajo" <giovannibajo@libero.it>
To: "Toon Moene" <toon@moene.indiv.nluug.nl>
Cc: <gcc-patches@gcc.gnu.org>, <gcc@gcc.gnu.org>,
	"Gerald Pfeifer" <gp@suse.de>
Subject: Re: RFC: Remove flags -fmove-all-movables and -freduce-all-givs.
Date: Mon, 13 Sep 2004 13:51:00 -0000	[thread overview]
Message-ID: <020101c49994$5130aad0$8b4e2597@bagio> (raw)
In-Reply-To: <4143E4C2.2020702@moene.indiv.nluug.nl>

Toon Moene wrote:

>>> * common.opt: Remove flags -fmove-all-movables and
>>> -freduce-all-givs.
>>> * loop-invariant.c (find_invariants_to_move):
>>> Remove all uses of flag_move_all_movables.
>>> * loop.c (move_movables): Remove all uses of
>>> flag_move_all_movables.
>>> (strength_reduce): Remove all uses of
>>> flag_reduce_all_givs.
>>> * doc/invoke.texi: Remove documentation of flags
>>> -fremove-all-movables and -freduce-all-givs.

Can you please update http://gcc.gnu.org/gcc-4.0/changes.html with also a
little rationale about why those options were removed? I thought we owe an
explanation to everybody that was using those flags and upgrade -- whether
their use was really succesfull on code generation or they only believed it
was.

Giovanni Bajo


  reply	other threads:[~2004-09-13 13:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-11 17:37 Toon Moene
2004-09-11 19:02 ` Richard Henderson
2004-09-12 11:39   ` Toon Moene
2004-09-13 13:51     ` Giovanni Bajo [this message]
2004-09-13 14:18       ` Joseph S. Myers
2004-09-13 23:51         ` Toon Moene
2004-09-17 16:30         ` Toon Moene

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='020101c49994$5130aad0$8b4e2597@bagio' \
    --to=giovannibajo@libero.it \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=gp@suse.de \
    --cc=toon@moene.indiv.nluug.nl \
    /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).