From: Toon Moene <toon@moene.indiv.nluug.nl>
To: "Joseph S. Myers" <jsm@polyomino.org.uk>
Cc: Giovanni Bajo <giovannibajo@libero.it>,
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 23:51:00 -0000 [thread overview]
Message-ID: <4146264B.4070901@moene.indiv.nluug.nl> (raw)
In-Reply-To: <Pine.LNX.4.61.0409131406080.22278@digraph.polyomino.org.uk>
Joseph S. Myers wrote:
> On Mon, 13 Sep 2004, Giovanni Bajo wrote:
>
>>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.
Thanks for bringing this to my attention - it will be taken care of in
the next time slot (i.e., the coming weekend :-).
> Also, the manual still contains the two paragraphs that followed the
> description of those options:
Ugh - I will not even attempt to dig up an explanation for this
oversight; I'm sorry. Thanks, Joseph.
--
Toon Moene - e-mail: toon@moene.indiv.nluug.nl - phone: +31 346 214290
Saturnushof 14, 3738 XG Maartensdijk, The Netherlands
Maintainer, GNU Fortran 77: http://gcc.gnu.org/onlinedocs/g77_news.html
A maintainer of GNU Fortran 95: http://gcc.gnu.org/fortran/
next prev parent reply other threads:[~2004-09-13 22:54 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
2004-09-13 14:18 ` Joseph S. Myers
2004-09-13 23:51 ` Toon Moene [this message]
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=4146264B.4070901@moene.indiv.nluug.nl \
--to=toon@moene.indiv.nluug.nl \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=giovannibajo@libero.it \
--cc=gp@suse.de \
--cc=jsm@polyomino.org.uk \
/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).