summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/signals
diff options
context:
space:
mode:
authorTodd Fiala <todd.fiala@gmail.com>2016-02-03 21:13:23 +0000
committerTodd Fiala <todd.fiala@gmail.com>2016-02-03 21:13:23 +0000
commit675bdcedff0879e14dae42383d9b25fc6fd25861 (patch)
tree389a7e60fa3704bb0f336c991989a8e204186ba4 /lldb/packages/Python/lldbsuite/test/python_api/signals
parentba043143a9fc9d59977d9c4bc54465603e43cecd (diff)
downloadbcm5719-llvm-675bdcedff0879e14dae42383d9b25fc6fd25861.tar.gz
bcm5719-llvm-675bdcedff0879e14dae42383d9b25fc6fd25861.zip
Address NDEBUG-related linkage issues for Value::assertModuleIsMaterialized()
The IR/Value class had a linkage issue present when LLVM was built as a library, and the LLVM library build time had different settings for NDEBUG than the client of the LLVM library. Clients could get into a state where the LLVM lib expected Value::assertModuleIsMaterialized() to be inline-defined in the header but clients expected that method to be defined in the LLVM library. See this llvm-commits thread for more details: http://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon-20160201/329667.html llvm-svn: 259695
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/signals')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud