https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117249
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> --- (In reply to Alexander Monakov from comment #3) > I think the right fix is to add a put_noreplace method that asserts > internally and transform incorrect gcc_assert (!...->put(...)) instances to > that. That would be definitely a decent fix. Though since this has been broken for 10 years now, maybe removing the ability to disable assert checking is the better way forward. I have not audited all gcc_asserts that have been added in the last 10 years to see if there are other issues that slipped in either.
