diff options
| author | Zola Bridges <zbrid@google.com> | 2020-05-02 16:53:34 -0700 |
|---|---|---|
| committer | Zola Bridges <zbrid@google.com> | 2020-05-04 10:01:40 -0700 |
| commit | 8d8fda49c99dcb854d0fb58422f513ae909770cd (patch) | |
| tree | f078f6a8b2fe781c1f0df267f99eb3388ea735de /llvm/tools/llvm-objdump/llvm-objdump.cpp | |
| parent | 09e4e9ff7b9ada6386f7cfc0aa150de6239541b1 (diff) | |
| download | llvm-8d8fda49c99dcb854d0fb58422f513ae909770cd.zip llvm-8d8fda49c99dcb854d0fb58422f513ae909770cd.tar.gz llvm-8d8fda49c99dcb854d0fb58422f513ae909770cd.tar.bz2 | |
[llvm][dfsan][NFC] Factor out fcn initialization
Summary:
Moving these function initializations into separate functions makes it easier
to read the runOnModule function. There is also precedent in the sanitizer code:
asan has a function ModuleAddressSanitizer::initializeCallbacks(Module &M). I
thought it made sense to break the initializations into two sets. One for the
compiler runtime functions and one for the event callbacks.
Tested with: check-all
Reviewed By: morehouse
Differential Revision: https://reviews.llvm.org/D79307
Diffstat (limited to 'llvm/tools/llvm-objdump/llvm-objdump.cpp')
0 files changed, 0 insertions, 0 deletions