diff options
| author | Amir Ayupov <aaupov@fb.com> | 2021-06-01 11:37:41 -0700 |
|---|---|---|
| committer | spupyrev <spupyrev@fb.com> | 2022-07-11 09:31:51 -0700 |
| commit | f921985a29fc9787b3ed98dbc897146cc3fd91f7 (patch) | |
| tree | b12bb8c4903702c6e0b7c3971940681025a72a83 /lldb/packages/Python/lldbsuite/test/configuration.py | |
| parent | c8a28ae214c08c8447a4eb42418585b2b3eef6fb (diff) | |
| download | llvm-f921985a29fc9787b3ed98dbc897146cc3fd91f7.zip llvm-f921985a29fc9787b3ed98dbc897146cc3fd91f7.tar.gz llvm-f921985a29fc9787b3ed98dbc897146cc3fd91f7.tar.bz2 | |
Rebase: [Facebook] Add clang driver options to test debug info and BOLT
Summary:
This is an essential piece of infrastructure for us to be
continuously testing debug info with BOLT. We can't only make changes
to a test repo because we need to change debuginfo tests to call BOLT,
hence, this diff needs to sit in our opensource repo. But when upstreaming
to LLVM, this should be kept BOLT-only outside of LLVM. When upstreaming,
we need to git diff and check all folders that are being modified by our
commits and discard this one (and leave as an internal diff).
To test BOLT in debuginfo tests, configure it with -DLLVM_TEST_BOLT=ON.
Then run check-lldb and check-debuginfo.
Manual rebase conflict history:
https://phabricator.intern.facebook.com/D29205224
https://phabricator.intern.facebook.com/D29564078
https://phabricator.intern.facebook.com/D33289118
https://phabricator.intern.facebook.com/D34957174
Test Plan:
tested locally
Configured with:
-DLLVM_ENABLE_PROJECTS="clang;lld;lldb;compiler-rt;bolt;debuginfo-tests"
-DLLVM_TEST_BOLT=ON
Ran test suite with:
ninja check-debuginfo
ninja check-lldb
Reviewers: #llvm-bolt
Subscribers: ayermolo, phabricatorlinter
Differential Revision: https://phabricator.intern.facebook.com/D35317341
Tasks: T92898286
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/configuration.py')
0 files changed, 0 insertions, 0 deletions