public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/54345] jump threading leaks e->aux heap memory
Date: Thu, 20 Sep 2012 11:13:00 -0000 [thread overview]
Message-ID: <bug-54345-4-yYwGSSxm9I@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54345-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54345
--- Comment #2 from rguenther at suse dot de <rguenther at suse dot de> 2012-09-20 11:12:36 UTC ---
On Thu, 20 Sep 2012, polacek at redhat dot com wrote:
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54345
>
> Marek Polacek <polacek at redhat dot com> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |polacek at redhat dot com
>
> --- Comment #1 from Marek Polacek <polacek at redhat dot com> 2012-09-20 08:16:55 UTC ---
> How can I reproduce this one? I've built gcc with '--enable-languages=c,c++
> --disable-bootstrap' and '--enable-languages=c,c++ --disable-bootstrap
> --enable-checking=valgrind', but then e.g.
> valgrind --leak-check=full --show-reachable=yes ./cc1
> ~/src/gcc/gcc/testsuite/gcc.dg/tree-ssa/ssa-dom-thread-2.c -O2 -fno-tree-vrp
> show nothing like this. (In that test we certainly run the DOM pass, thus also
> jump-threading.) Or am I doing something stupid?
It obviously depends on the testcase. I was using something very large.
next prev parent reply other threads:[~2012-09-20 11:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-21 12:27 [Bug tree-optimization/54345] New: " rguenth at gcc dot gnu.org
2012-09-20 8:17 ` [Bug tree-optimization/54345] " polacek at redhat dot com
2012-09-20 11:13 ` rguenther at suse dot de [this message]
2012-09-21 15:11 ` polacek at redhat dot com
2012-09-24 8:52 ` rguenther at suse dot de
2012-09-28 13:04 ` mpolacek at gcc dot gnu.org
2021-08-14 22:21 ` pinskia at gcc dot gnu.org
2024-02-20 14:02 ` 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-54345-4-yYwGSSxm9I@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).