[Bug libstdc++/20150] allocate(0) consistency checks

2021-05-04 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=20150 Jonathan Wakely changed: What|Removed |Added Resolution|--- |WONTFIX Status|ASSIGNED

[Bug libstdc++/20150] allocate(0) consistency checks

2021-05-04 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=20150 Richard Biener changed: What|Removed |Added Status|NEW |ASSIGNED

[Bug libstdc++/20150] allocate(0) consistency checks

2018-08-24 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=20150 --- Comment #1 from Jonathan Wakely --- I thought this was by design, because it ensures we never return a null pointer, and that any two calls to allocate will return different values. I'm inclined to close this as WONTFIX.

[Bug libstdc++/20150] allocate(0) consistency checks

2005-05-26 Thread pinskia at gcc dot gnu dot org
-- What|Removed |Added Status|UNCONFIRMED |NEW Ever Confirmed||1 Last reconfirmed|-00-00 00:00:00