From: Gerald Pfeifer <gerald@pfeifer.com>
To: Thomas Koenig <tkoenig@netcologne.de>
Cc: fortran@gcc.gnu.org, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch, changes, fortran, committed] Mention -ffrontend-optimize and -Wfunction-elimination
Date: Sun, 10 Apr 2011 20:31:00 -0000 [thread overview]
Message-ID: <alpine.LNX.2.00.1104102230220.3701@gerinyyl.fvgr> (raw)
In-Reply-To: <4DA1A7FF.1040006@netcologne.de>
On Sun, 10 Apr 2011, Thomas Koenig wrote:
> I committed the following as obvious, after verifying with the
> w3c validator.
Thanks! I followed up with a minor editorial change.
Gerald
Index: changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.7/changes.html,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- changes.html 10 Apr 2011 09:28:44 -0000 1.7
+++ changes.html 10 Apr 2011 10:39:13 -0000 1.8
@@ -64,13 +64,14 @@
<li>Front-end optimizations can now be selected by the
<code>-ffrontend-optimize</code> option and deselected by
the <code>-fno-frontend-optimize</code> option.</li>
- <li>When front-end optimization removes a function call, the
- <code>-Wfunction-elimination</code> warns about the removal.</li>
+ <li>When front-end optimization removes a function call,
+ <code>-Wfunction-elimination</code> warns about that.</li>
<li>When performing front-end-optimzation, the
<code>-faggressive-function-elimination</code> option
allows the removal of duplicate function calls even for impure
functions.</li>
</ul>
+
<h3>Java (GCJ)</h3>
<h2 id="targets">New Targets and Target Specific Improvements</h2>
prev parent reply other threads:[~2011-04-10 20:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-10 12:52 Thomas Koenig
2011-04-10 20:31 ` Gerald Pfeifer [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=alpine.LNX.2.00.1104102230220.3701@gerinyyl.fvgr \
--to=gerald@pfeifer.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=tkoenig@netcologne.de \
/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).