[PATCH] [analyzer] Assume new returns non-null even under -fno-exceptions

[Pavel Labath]

Hi jordan_rose,

-fno-exceptions does not implicitly attach a nothrow specifier to every operator
new. Even in this mode, non-nothrow new must not return a null pointer. Failure
to allocate memory can be signalled by other means, or just by killing the
program. This behaviour is consistent with the compiler - even with
-fno-exceptions, the generated code never tests for null (and would segfault if
the opeator actually happened to return null).

http://llvm-reviews.chandlerc.com/D1528

Files:
  lib/StaticAnalyzer/Core/ExprEngineCXX.cpp
  test/Analysis/NewDelete-path-notes.cpp
  test/Analysis/new-with-exceptions.cpp
-------------- next part --------------
A non-text attachment was scrubbed...
Name: D1528.1.patch
Type: text/x-patch
Size: 19495 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/cfe-commits/attachments/20130827/831f0790/attachment.bin>