public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/32102] -Wall stomps on -Wstrict-overflow
Date: Tue, 22 Jan 2008 14:47:00 -0000 [thread overview]
Message-ID: <20080122142210.22323.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32102-11211@http.gcc.gnu.org/bugzilla/>
------- Comment #14 from manu at gcc dot gnu dot org 2008-01-22 14:22 -------
When you try to do things faster, you end up taking more time.
Anyway, fixed for GCC 4.3.
Ian,
do you think this should/could be backported to GCC 4.2 or should we just close
it as fixed?
--
manu at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |4.3.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32102
next prev parent reply other threads:[~2008-01-22 14:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-27 2:46 [Bug c/32102] New: " mec at google dot com
2007-05-27 3:45 ` [Bug c/32102] " pinskia at gcc dot gnu dot org
2007-05-29 13:48 ` ian at airs dot com
2008-01-18 18:48 ` manu at gcc dot gnu dot org
2008-01-18 19:11 ` ismail at pardus dot org dot tr
2008-01-18 19:30 ` manu at gcc dot gnu dot org
2008-01-18 19:42 ` ismail at pardus dot org dot tr
2008-01-19 8:09 ` manu at gcc dot gnu dot org
2008-01-20 14:40 ` manu at gcc dot gnu dot org
2008-01-21 1:52 ` manu at gcc dot gnu dot org
2008-01-21 20:50 ` ian at airs dot com
2008-01-21 21:01 ` manu at gcc dot gnu dot org
2008-01-22 14:20 ` manu at gcc dot gnu dot org
2008-01-22 14:46 ` manu at gcc dot gnu dot org
2008-01-22 14:47 ` manu at gcc dot gnu dot org [this message]
2008-01-23 6:43 ` ian at airs dot com
2008-01-27 18:52 ` manu at gcc dot gnu dot org
2008-01-27 18:55 ` manu 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=20080122142210.22323.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).