https://gcc.gnu.org/bugzilla/show_bug.cgi?id=123872
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2026-01-29
Ever confirmed|0 |1
Status|UNCONFIRMED |NEW
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
I agree this makes sense.
Currently it's not defined for -fno-aligned-new, which is the default for C++14
and can be used for C++17 and later.
We have __BIGGEST_ALIGNMENT__ defined unconditionally, with a fixed value for
the target, but I don't think that's guaranteed to be the same as the default
alignment you get for -faligned-new
N.B. this would mean you must not use #ifdef __STDCPP_DEFAULT_NEW_ALIGNMENT__
to check for std::align_val_t and aligned-new support. But that's OK, you
should use __cpp_aligned_new for that anyway.
