From: Gerald Pfeifer <gerald@pfeifer.com>
To: gcc-patches@gcc.gnu.org, Mark Mitchell <mark@codesourcery.com>
Subject: [wwwdocs] PATCH for -Wimplicit-double
Date: Sun, 17 Oct 2010 16:36:00 -0000 [thread overview]
Message-ID: <alpine.LNX.2.00.1010171806190.2945@acrux.dbai.tuwien.ac.at> (raw)
In-Reply-To: <4C8529BB.5000801@codesourcery.com>
On Mon, 6 Sep 2010, Mark Mitchell wrote:
>> OK, here's the version I checked in. I will now implement the C++
>> version of the warning.
> Here's the C++ patch.
I noticed this hasn't made it to the GCC 4.6 release notes yet,
thus applied the patch below. Happy to make changes to improve
upon this.
Gerald
Index: changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.6/changes.html,v
retrieving revision 1.50
diff -u -3 -p -r1.50 changes.html
--- changes.html 6 Oct 2010 14:51:49 -0000 1.50
+++ changes.html 17 Oct 2010 16:05:46 -0000
@@ -106,6 +106,14 @@
<h3>C family</h3>
+ <ul>
+ <li>A new warning, enabled by <code>-Wno-double-promotion</code>,
+ has been added that warns about cases where a value of type
+ <code>float</code> is implicitly promoted to <code>double</code>.
+ This is especially helpful for CPUs that handle the former in
+ hardware, but emulate the latter in software.</li>
+ </ul>
+
<h3 id="C">C</h3>
<ul>
prev parent reply other threads:[~2010-10-17 16:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-03 16:04 RFA: PATCH: -Wimplicit-double Mark Mitchell
2010-09-03 17:38 ` Mark Mitchell
2010-09-03 17:45 ` Manuel López-Ibáñez
2010-09-03 17:51 ` Manuel López-Ibáñez
2010-09-03 18:06 ` Mark Mitchell
2010-09-03 19:03 ` Manuel López-Ibáñez
2010-09-03 19:13 ` Mark Mitchell
2010-09-04 8:35 ` Daniel Jacobowitz
2010-09-04 12:47 ` Gabriel Dos Reis
2010-09-05 22:15 ` Mark Mitchell
2010-09-06 17:57 ` Mark Mitchell
2010-10-17 16:36 ` 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.1010171806190.2945@acrux.dbai.tuwien.ac.at \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mark@codesourcery.com \
/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).