[Bug tree-optimization/54345] jump threading leaks e->aux heap memory
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54345 Richard Biener changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #7 from Richard Biener --- I think this was meanwhile fixed.
[Bug tree-optimization/54345] jump threading leaks e->aux heap memory
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54345 --- Comment #6 from Andrew Pinski --- There has been so many changes to this code since GCC 4.8.0 dealing with the allocations of this pointer. I can't tell if this has been fixed really.
[Bug tree-optimization/54345] jump threading leaks e-aux heap memory
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54345 Marek Polacek mpolacek at gcc dot gnu.org changed: What|Removed |Added CC||mpolacek at gcc dot gnu.org --- Comment #5 from Marek Polacek mpolacek at gcc dot gnu.org 2012-09-28 13:04:12 UTC --- Sorry, I'm still not seeing the leak. Tried testcase in PR46590 as well as in some other memory-hog bugs, e.g. PR54489.
[Bug tree-optimization/54345] jump threading leaks e-aux heap memory
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54345 --- Comment #4 from rguenther at suse dot de rguenther at suse dot de 2012-09-24 08:52:06 UTC --- On Fri, 21 Sep 2012, polacek at redhat dot com wrote: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54345 --- Comment #3 from Marek Polacek polacek at redhat dot com 2012-09-21 15:11:08 UTC --- Hmm. I hoped that something like this will show the leak, but no (it does a lot of threading with -O2--through conditionals, through loop headers and also through latches). But obviously it's not enough. Any ideas, please? ISTR I recognized this on the testcase for PR46590
[Bug tree-optimization/54345] jump threading leaks e-aux heap memory
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54345
--- Comment #3 from Marek Polacek polacek at redhat dot com 2012-09-21
15:11:08 UTC ---
Hmm. I hoped that something like this will show the leak, but no (it does a
lot of threading with -O2--through conditionals, through loop headers and also
through latches). But obviously it's not enough. Any ideas, please?
extern void bla (void);
extern void bar (void);
extern void foo (void);
void
thread_through_condition (int a, int b)
{
#define E if (a b)\
bla ();\
else\
bar ();\
if (a = b)\
foo ();
#define E10 E E E E E E E E E E
#define E100 E10 E10 E10 E10 E10 E10 E10 E10 E10 E10
#define E1000 E100 E100 E100 E100 E100 E100 E100 E100 E100 E100
#define EE E1000 E1000
EE
}
void
thread_entry_through_header (void)
{
int i;
#define A for (i = 0; i 42; ++i) \
bla ();
#define A10 A A A A A A A A A A
#define A100 A10 A10 A10 A10 A10 A10 A10 A10 A10 A10
#define A1000 A100 A100 A100 A100 A100 A100 A100 A100 A100 A100
#define AA A1000 A1000 A1000 A1000 A1000
AA
}
void
thread_latch_through_header (void)
{
int i = 0;
int first;
#define L first = 1; i = 0;\
do {\
if (first)\
foo ();\
first = 0;\
bla ();\
} while (i++ 100);
#define L10 L L L L L L L L L L
#define L100 L10 L10 L10 L10 L10 L10 L10 L10 L10 L10
#define L1000 L100 L100 L100 L100 L100 L100 L100 L100 L100 L100
L1000
}
[Bug tree-optimization/54345] jump threading leaks e-aux heap memory
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?
[Bug tree-optimization/54345] jump threading leaks e-aux heap memory
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.
