https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103162
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|INVALID |---
Status|RESOLVED |NEW
Ever confirmed|0 |1
Last reconfirmed| |2021-11-09
--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
I think I've convinced myself that the non-null requirement doesn't apply here.
A custom memory_resource can do whatever it wants, so the attribute can't be
used here.
It can be used on the do_allocate overriders in the standard memory resources,
although that won't be very useful in practice unless the compiler is able to
devirtualize and inline the calls.
