Displaying 1 result from an estimated 1 matches for "63a2b859".
2019 Dec 02
2
Avoiding function addresses in llvm_prf_data when value profiling is disabled
I encountered an issue when enabling code coverage for Android and would
like to confirm my findings and ask for suggestions.
Here is my finding:
When -fprofile-instr-generate, an llvm_prf_data section gets created that
has entries for each function in the TU. One of the entries is
FunctionAddr which holds the address of the function. Underneath, it is a
relocation so it gets patched with the