public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/41574] Distribute floating point expressions causes bad code.
Date: Mon, 05 Oct 2009 10:00:00 -0000 [thread overview]
Message-ID: <20091005100020.663.qmail@sourceware.org> (raw)
In-Reply-To: <bug-41574-14703@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from ebotcazou at gcc dot gnu dot org 2009-10-05 10:00 -------
> The ChangeLog entry is wrong.
And folks from Google shouldn't feel entitled to break a freeze imposed by
other folks from Google even if, yes, it is annoyingly long. :-)
--
ebotcazou at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ebotcazou at gcc dot gnu dot
| |org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41574
next prev parent reply other threads:[~2009-10-05 10:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-05 8:01 [Bug rtl-optimization/41574] New: " dougkwan at google dot com
2009-10-05 9:09 ` [Bug rtl-optimization/41574] " dougkwan at gcc dot gnu dot org
2009-10-05 9:32 ` ramana at gcc dot gnu dot org
2009-10-05 9:48 ` jakub at gcc dot gnu dot org
2009-10-05 10:00 ` ebotcazou at gcc dot gnu dot org [this message]
2009-10-05 15:44 ` dougkwan at google dot com
2009-10-05 15:49 ` dougkwan at google dot com
2009-10-08 22:17 ` dougkwan at gcc dot gnu dot org
2009-10-08 22:20 ` dougkwan at google dot com
2009-10-15 10:44 ` [Bug rtl-optimization/41574] Distribute floating point expressions causes bad code [4.4 only] ramana at gcc dot gnu dot org
2009-10-20 6:23 ` dougkwan at google dot com
2009-12-10 15:21 ` ramana at gcc dot gnu dot org
2009-12-11 11:22 ` ramana at gcc dot gnu dot org
2009-12-11 17:47 ` ramana at gcc dot gnu dot org
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=20091005100020.663.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).