On 7/27/20 11:51 AM, Jan Hubicka wrote:
On 7/27/20 9:11 AM, Richard Biener wrote:
OK. I guess the previous code tried to use less memory.
It did. But I didn't realize that such exact growth would lead
to a massive reallocation for huge apps like chromium.
I'm going to backport the patch older releases as well.
Thank you! Did it solved the the Chromium problem?
Yes, I verified that.
I guess I can try
to do some profiling since this problem did not show on Firefox (that i
find odd given that Firefox is just about half of the size).
Yep, I'm also surprised about it.
Perhaps glibc has some stupid limit in realloc that makes it to behave
in a silly way for very large arrays?
Dunno :P
Martin
Honza
Martin
