https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117727
--- Comment #4 from Timm Bäder <tbaeder at redhat dot com> --- (In reply to Jakub Jelinek from comment #2) > I thought all the bits of the type are padding bits (given that reads of > std::nullptr_t typed objects just don't read any of the bits and simply > result in nullptr). Is this (all bits if a nullptr_t being padding bits) in the spec or are you referring to gcc's implementation? (In reply to Andrew Pinski from comment #3) > So in summary all 3 compilers have different behavior. FWIW I opened https://github.com/llvm/llvm-project/issues/117166 on the clang side.