https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111050
--- Comment #3 from François Dumont <fdumont at gcc dot gnu.org> --- For sure _Hash_node layout didn't change, that's why I couldn't think of any abi issue here. I see that you already had the solution ! It was some kind of test then, I failed :-). Did you try it ? If you already have the use case on your side to reproduce the explosion it should be rather easy to confirm that adding: [[__gnu__::__always_inline__]] on _M_next member fixes the issue.
