[Bug middle-end/90959] hash_map can be copied but leads to a double-free after assignment

2022-03-17 Thread msebor at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90959 Martin Sebor changed: What|Removed |Added Status|ASSIGNED|NEW Assignee|msebor at gcc dot

[Bug middle-end/90959] hash_map can be copied but leads to a double-free after assignment

2020-03-05 Thread msebor at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90959 Martin Sebor changed: What|Removed |Added Status|WAITING |ASSIGNED Assignee|unassigned at

[Bug middle-end/90959] hash_map can be copied but leads to a double-free after assignment

2020-01-27 Thread marxin at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90959 Martin Liška changed: What|Removed |Added Status|UNCONFIRMED |WAITING Last reconfirmed|

[Bug middle-end/90959] hash_map can be copied but leads to a double-free after assignment

2019-06-24 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90959 --- Comment #1 from Richard Biener --- IIRC Jason added the constructor because the C++ FE does this. I think assignment is bad style so just delete that (or declare and not define for old C++ - IIRC we do have = deleted macros in system.h or an