diff options
| author | Maksim Panchenko <maks@fb.com> | 2025-05-01 15:09:09 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-05-01 15:09:09 -0700 |
| commit | 7d6fda4fd3a529bc3e14a2a71ea6ab33883757d2 (patch) | |
| tree | cc47f5286f38f37cc4e90961f1bcdbcdb8db33dd /lldb/test/API/python_api | |
| parent | 472c211f58f4169fe18f7941bb6b519e5425e621 (diff) | |
| download | llvm-7d6fda4fd3a529bc3e14a2a71ea6ab33883757d2.zip llvm-7d6fda4fd3a529bc3e14a2a71ea6ab33883757d2.tar.gz llvm-7d6fda4fd3a529bc3e14a2a71ea6ab33883757d2.tar.bz2 | |
[BOLT] Run PatchEntries pass before LongJmp (#137236)
With --force-patch option, every original function entry point is
overwritten with a trampoline to a new version of the function to
prevent the execution of the original code.
If the function size is too small for the trampoline code, we are forced
to bail out on rewriting the function. That presented a problem on
AArch64 due to LongJmp pass that assumed the presence of the new copy of
the function. If the new copy was not emitted it could have lead to a
relocation overflow.
Run PatchEntries pass before LongJmp and make the latter aware of the
functions that are not going to be emitted. Make --force-patch option
behavior on AArch64 consistent with other architectures.
Diffstat (limited to 'lldb/test/API/python_api')
0 files changed, 0 insertions, 0 deletions