aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/CodeGen/MachineBlockPlacement.cpp
diff options
context:
space:
mode:
authorWalter Erquinigo <a20012251@gmail.com>2023-10-05 20:17:48 -0400
committerGitHub <noreply@github.com>2023-10-05 20:17:48 -0400
commit87c6ff6da82a1288ce5c80370d5d8cdd4c20220d (patch)
treeb7e85d049eb5143ba69b029a02fd54b4155f8799 /llvm/lib/CodeGen/MachineBlockPlacement.cpp
parent8f397e04e5ce87fb5ff99d6659ba959c22ea926c (diff)
downloadllvm-87c6ff6da82a1288ce5c80370d5d8cdd4c20220d.zip
llvm-87c6ff6da82a1288ce5c80370d5d8cdd4c20220d.tar.gz
llvm-87c6ff6da82a1288ce5c80370d5d8cdd4c20220d.tar.bz2
[LLDB] Allow specifying a custom exports file (#68013)
LLDB has the cmake flag `LLDB_EXPORT_ALL_SYMBOLS` that exports the lldb, lldb_private namespaces, as well as other symbols like python and lua (see `lldb/source/API/liblldb-private.exports`). However, not all symbols in lldb fall into these categories and in order to get access to some symbols that live in plugin folders (like dwarf parsing symbols), it's useful to be able to specify a custom exports file giving more control to the developer using lldb as a library. This adds the new cmake flag `LLDB_EXPORT_ALL_SYMBOLS_EXPORTS_FILE` that is used when `LLDB_EXPORT_ALL_SYMBOLS` is enabled to specify that custom exports file. This is a follow up of https://github.com/llvm/llvm-project/pull/67851
Diffstat (limited to 'llvm/lib/CodeGen/MachineBlockPlacement.cpp')
0 files changed, 0 insertions, 0 deletions