http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53779
William J. Schmidt <wschmidt at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aoliva at gcc dot gnu.org --- Comment #3 from William J. Schmidt <wschmidt at gcc dot gnu.org> 2012-06-26 15:07:33 UTC --- I wonder if the recent changes to var-tracking.c contain the possibility for a double-free. I think it's not directly due to my patch for the following reason: This has happened on two different working patches recently. One makes memory allocation changes in the vectorizer; the other made memory allocation changes in IVOPTS. In both cases, the stack was nearly the same -- blowing up when freeing some memory in the var-tracking phase. In one case it was a call to free_alloc_pool, in the other a call to delete_htab. Copying Alexandre for his opinion. What do you think?