https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87271
--- Comment #4 from rguenther at suse dot de <rguenther at suse dot de> --- On Wed, 12 Sep 2018, jakub at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87271 > > Jakub Jelinek <jakub at gcc dot gnu.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |jakub at gcc dot gnu.org > > --- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> --- > You mean like mtrace in glibc? > Another option is try valgrind. Yeah, it's said to not work on freebsd. valgrind seems clean on trunk x86_64-linux and I think that means everything is OK there... I've just verified hash-map construction works as desired. I wonder if side-stepping the small-object allocators by changing the reserve_exact (2) to say reserve_exact (16) would change things... That is, I'm absolutely not ruling out an allocator issue (try tcmalloc?!)
