public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/47903] [4.5/4.6 Regression] var-tracking.c: valgrind error
Date: Sat, 26 Feb 2011 16:23:00 -0000 [thread overview]
Message-ID: <bug-47903-4-3mYdMRtP3w@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47903-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47903
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|var-tracking.c: valgrind |[4.5/4.6 Regression]
|error |var-tracking.c: valgrind
| |error
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-02-26 15:42:29 UTC ---
I can reproduce it even with 4.5.1 and obviously when it hits in var-tracking.c
(loc_cmp), it is a 4.5/4.6 regression, as 4.4 and earlier didn't do VALUE based
tracking.
next prev parent reply other threads:[~2011-02-26 15:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-26 9:55 [Bug c++/47903] New: " dcb314 at hotmail dot com
2011-02-26 15:42 ` [Bug middle-end/47903] " jakub at gcc dot gnu.org
2011-02-26 16:04 ` jakub at gcc dot gnu.org
2011-02-26 16:23 ` jakub at gcc dot gnu.org [this message]
2011-02-27 19:45 ` [Bug middle-end/47903] [4.5/4.6 Regression] " jakub at gcc dot gnu.org
2011-02-27 19:46 ` [Bug middle-end/47903] [4.5 " jakub at gcc dot gnu.org
2011-03-25 20:10 ` jakub at gcc dot gnu.org
2011-06-27 16:36 ` jakub at gcc dot gnu.org
2011-10-10 12:43 ` rguenth at gcc dot gnu.org
2012-06-20 12:57 ` rguenth at gcc dot gnu.org
2012-06-20 13:56 ` rguenth at gcc dot gnu.org
2012-06-20 14:49 ` rguenth 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-47903-4-3mYdMRtP3w@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).