summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/expression_command/call-function
diff options
context:
space:
mode:
authorShoaib Meenai <smeenai@fb.com>2017-10-05 02:18:08 +0000
committerShoaib Meenai <smeenai@fb.com>2017-10-05 02:18:08 +0000
commita4a3d40eb6497a7a9595949a41b19dce1d48e6bd (patch)
tree7f8167e09036593fff67e47ba7f658f7a3f32bfa /lldb/packages/Python/lldbsuite/test/expression_command/call-function
parent03e77c64f180d9411364e6a017489e016024d874 (diff)
downloadbcm5719-llvm-a4a3d40eb6497a7a9595949a41b19dce1d48e6bd.tar.gz
bcm5719-llvm-a4a3d40eb6497a7a9595949a41b19dce1d48e6bd.zip
[libc++] Clarify names of ABI forcing macros
Make it clear that these are intended only to force a specific ABI when the autodetection would give the wrong result by renaming the cmake options and adding separate forcing macros, as suggested by EricWF in the post-commit review of r314949 and further discussed on IRC. llvm-svn: 314965
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/expression_command/call-function')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud