public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pedro.larroy at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/49651] [4.4/4.5 Regression] nested lambdas and -O3 produced incorrect integer variable increments
Date: Mon, 01 Aug 2011 16:00:00 -0000 [thread overview]
Message-ID: <bug-49651-4-zqGW19pHkr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49651-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49651
--- Comment #14 from Pedro Larroy <pedro.larroy at gmail dot com> 2011-08-01 15:59:23 UTC ---
(In reply to comment #13)
> Fixed for 4.6.2 and trunk sofar.
great! thanks.
next prev parent reply other threads:[~2011-08-01 16:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-05 20:15 [Bug c++/49651] New: [C++0x] " pedro.larroy at gmail dot com
2011-07-05 20:30 ` [Bug c++/49651] " pedro.larroy at gmail dot com
2011-07-05 21:54 ` redi at gcc dot gnu.org
2011-07-05 22:24 ` pedro.larroy at gmail dot com
2011-07-05 23:54 ` redi at gcc dot gnu.org
2011-07-12 14:39 ` [Bug tree-optimization/49651] " jason at gcc dot gnu.org
2011-07-12 15:21 ` rguenth at gcc dot gnu.org
2011-07-13 12:32 ` rguenth at gcc dot gnu.org
2011-07-14 12:27 ` rguenth at gcc dot gnu.org
2011-07-14 12:37 ` rguenth at gcc dot gnu.org
2011-07-14 13:02 ` [Bug tree-optimization/49651] [4.4/4.5/4.6/4.7 Regression] " rguenth at gcc dot gnu.org
2011-07-14 14:54 ` rguenth at gcc dot gnu.org
2011-07-14 14:57 ` rguenth at gcc dot gnu.org
2011-07-14 15:01 ` [Bug tree-optimization/49651] [4.4/4.5 " rguenth at gcc dot gnu.org
2011-08-01 14:09 ` rguenth at gcc dot gnu.org
2011-08-01 16:00 ` pedro.larroy at gmail dot com [this message]
2012-01-04 9:48 ` rguenth at gcc dot gnu.org
2012-01-04 9:50 ` rguenth at gcc dot gnu.org
2012-01-04 11:55 ` rguenth at gcc dot gnu.org
2012-01-04 11:56 ` [Bug tree-optimization/49651] [4.4 " rguenth at gcc dot gnu.org
2012-03-13 17:00 ` jakub at gcc dot gnu.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=bug-49651-4-zqGW19pHkr@http.gcc.gnu.org/bugzilla/ \
--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).