[all-commits] [llvm/llvm-project] 02482f: [BOLT] Properly validate relocations against inter...
Maksim Panchenko via All-commits
all-commits at lists.llvm.org
Sat Dec 6 14:39:29 PST 2025
Branch: refs/heads/main
Home: https://github.com/llvm/llvm-project
Commit: 02482f42739e5b16035f4169923cb6abe0bb9698
https://github.com/llvm/llvm-project/commit/02482f42739e5b16035f4169923cb6abe0bb9698
Author: Maksim Panchenko <maks at fb.com>
Date: 2025-12-06 (Sat, 06 Dec 2025)
Changed paths:
M bolt/include/bolt/Core/BinaryFunction.h
M bolt/lib/Core/BinaryFunction.cpp
M bolt/test/X86/unclaimed-jt-entries.s
M bolt/test/runtime/X86/unclaimed-jt-entries.s
Log Message:
-----------
[BOLT] Properly validate relocations against internals of a function (#167451)
Validation of data relocations targeting internals of a function was
happening based on offsets inside a function. As a result, if multiple
relocations were targeting the same offset, and one of the relocations
was verified, e.g. as belonging to a jump table, then all relocations
targeting the offset would be considered verified and valid.
Now that we are tracking relocations pointing inside every function, we
can do a better validation based on the location of the relocation.
E.g., if a relocation belongs to a jump table only that relocation will
be accounted for and other relocations pointing to the same address will
be evaluated independently.
To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications
More information about the All-commits
mailing list