Re: [PATCH] Do not allocate huge array in output_in_order.

2020-07-31 Thread Jan Hubicka
> We noticed that when analyzing LTRANS memory peak that happens right > after the start: > https://gist.github.com/marxin/223890df4d8d8e490b6b2918b77dacad > > In case of chrome, we have symtab->order == 200M, so we allocate > 16B * 200M = 3.2GB. 200M is very large number even for overall number

[PATCH] Do not allocate huge array in output_in_order.

2020-07-30 Thread Martin Liška
We noticed that when analyzing LTRANS memory peak that happens right after the start: https://gist.github.com/marxin/223890df4d8d8e490b6b2918b77dacad In case of chrome, we have symtab->order == 200M, so we allocate 16B * 200M = 3.2GB. Patch can bootstrap on x86_64-linux-gnu and survives regressi