https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94355
--- Comment #15 from Benjamin Priour <vultkayn at gcc dot gnu.org> --- (In reply to Jonathan Wakely from comment #14) > [...snip...] > > See the -fcheck-new option: > > Check that the pointer returned by "operator new" is non-null before > attempting to modify the storage allocated. This check is normally > unnecessary because the C++ standard specifies that "operator new" only > returns 0 if it is declared "throw()", in which case the compiler always > checks the return value even without this option. In all other cases, when > "operator new" has a non-empty exception specification, memory exhaustion is > signalled by throwing "std::bad_alloc". See also new (nothrow). Should we use the above flag's value to also optionally disable the analyzer warnings on operator new possibly returning NULL? Or maybe there could be an additional flag -fanalyzer-new-returns-null, turned 'on' by default. Having such capability would be useful to run the analyzer against itself, as GCC is built without exceptions (thus every operator new possibly returns NULL).
