Right now we annotate C++'s operator new with noalias attribute,
which very much is healthy for optimizations.
However as per [[ http://eel.is/c++draft/basic.stc.dynamic.allocation | [basic.stc.dynamic.allocation] ]],
there are more promises on global operator new, namely:
- non-std::nothrow_t operator new *never* returns nullptr
- If std::align_val_t align parameter is taken, the pointer will also be align-aligned
global operator new-returned pointer is __STDCPP_DEFAULT_NEW_ALIGNMENT__-alignedIt's more caveated than that.
Supplying this information may not cause immediate landslide effects
on any specific benchmarks, but it for sure will be healthy for optimizer
in the sense that the IR will better reflect the guarantees provided in the source code.
The caveat is -fno-assume-sane-operator-new, which currently prevents emitting noalias
attribute, and is automatically passed by Sanitizers (PR16386) - should it also cover these attributes?
The problem is that the flag is back-end-specific, as seen in test/Modules/explicit-build-flags.cpp.
But while it is okay to add noalias metadata in backend, we really should be adding at least
the alignment metadata to the AST, since that allows us to perform sema checks on it.