From: "Joseph S. Myers" <jsm@polyomino.org.uk>
To: Giovanni Bajo <giovannibajo@libero.it>
Cc: Toon Moene <toon@moene.indiv.nluug.nl>,
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 14:18:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.61.0409131406080.22278@digraph.polyomino.org.uk> (raw)
In-Reply-To: <020101c49994$5130aad0$8b4e2597@bagio>
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.
Also, the manual still contains the two paragraphs that followed the
description of those options:
These two options are intended to be removed someday, once
they have helped determine the efficacy of various
approaches to improving loop optimizations.
Please contact @w{@email{gcc@@gcc.gnu.org}}, and describe how use of
these options affects the performance of your production code.
Examples of code that runs @emph{slower} when these options are
@emph{enabled} are very valuable.
--
Joseph S. Myers http://www.srcf.ucam.org/~jsm28/gcc/
http://www.srcf.ucam.org/~jsm28/gcc/#c90status - status of C90 for GCC 4.0
jsm@polyomino.org.uk (personal mail)
jsm28@gcc.gnu.org (Bugzilla assignments and CCs)
next prev parent reply other threads:[~2004-09-13 14:07 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 [this message]
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=Pine.LNX.4.61.0409131406080.22278@digraph.polyomino.org.uk \
--to=jsm@polyomino.org.uk \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=giovannibajo@libero.it \
--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).