On 02/25/2016 07:02 PM, David Malcolm wrote:
> Was this tested with "jit" in --enable-languages? I ask because
> toplev::main can be run repeatedly by libgccjit, and it looks like
> nothing can reset after_memory_report. (Though I don't typically build
> with --enable-gather-detailed-mem-stats,
On Thu, 2016-02-25 at 12:07 +0100, Martin Liška wrote:
> Hello.
>
> As discussed in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69919#c3
> , following patch
> guards usage of memory statistics infrastructure after a
> mem_alloc_description is already
> destructed.
>
> Patch can lto-bootstrap on
On Thu, Feb 25, 2016 at 12:07 PM, Martin Liška wrote:
> Hello.
>
> As discussed in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69919#c3,
> following patch
> guards usage of memory statistics infrastructure after a
> mem_alloc_description is already
> destructed.
>
> Patch can lto-bootstrap on x
Hello.
As discussed in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69919#c3,
following patch
guards usage of memory statistics infrastructure after a mem_alloc_description
is already
destructed.
Patch can lto-bootstrap on x86_64-linux-gnu with
--enable-gather-detailed-mem-stats and
survives b
