diff options
| author | Daniel Dunbar <daniel@zuster.org> | 2012-03-05 21:02:05 +0000 |
|---|---|---|
| committer | Daniel Dunbar <daniel@zuster.org> | 2012-03-05 21:02:05 +0000 |
| commit | e5617c79e4e13ce1fb9d408aec299e03db11b3e5 (patch) | |
| tree | 0a48f6ac9158ad15c0c78e4f6cf2aa17c7d6b89b /lldb/scripts/Python/python-extensions.swig | |
| parent | 9bd4be9657fa296d562e17f5b975ee130f9f127f (diff) | |
| download | llvm-e5617c79e4e13ce1fb9d408aec299e03db11b3e5.zip llvm-e5617c79e4e13ce1fb9d408aec299e03db11b3e5.tar.gz llvm-e5617c79e4e13ce1fb9d408aec299e03db11b3e5.tar.bz2 | |
ASTContext: Don't use nothrow specifications on the new operators for allocating
from the ASTContext.
- Doing so requires the compiler to generate null checks against the returned
result, but the BumpPtrAllocator never returns null pointers.
- The optimizer can usually eliminate such checks, but not always, so this
gives us tighter codegen in some places.
- It would be really nice if we could just use __builtin_unreachable or
something to tell the optimizer that the allocator never returns null, but
LLVM isn't currently that smart.
llvm-svn: 152060
Diffstat (limited to 'lldb/scripts/Python/python-extensions.swig')
0 files changed, 0 insertions, 0 deletions