https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68446
David Malcolm <dmalcolm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2016-01-15
Ever confirmed|0 |1
--- Comment #6 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
(In reply to Martin Liška from comment #5)
> Hi David.
>
> Removal of lazy initialization:
[...]
> Introduces back the memory leak that was removed in r230264:
> $ valgrind --leak-check=yes --trace-children=yes ./xgcc -B. -c
> /home/marxin/Programming/gcc3/gcc/testsuite/g++.dg/ext/mv1.C -O2 -fPIC
[...]
Thanks.
I've posted:
https://gcc.gnu.org/ml/gcc-patches/2016-01/msg01135.html
which fixes that leak in a slightly different way, and fixes the issues seen by
the jit in this PR.
> Using trunk with the patch you suggest, I see invalid write operation by
> valgrind (same command line):
>
> ==27543== Invalid write of size 8
I see that also; I've moved that part of the patch to:
https://gcc.gnu.org/ml/gcc-patches/2016-01/msg01136.html
