-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bug] No checking about "requires the first loadable segment to be executable". #171
Comments
"Why autofdo doesn't use propeller's code about runtime address to binary address?" |
AutoFDO delegates the mapping work to quipper, whereas propeller writes its own logic to handle this. A little bit history: AutoFDO predates propeller, and when we wrote propeller, we found that having the logic in propeller is the best option, since it is easier and quicker to use, and easier to debug.
perf_data_converter, which is included in AutoFDO as a submodule, is responsible for calculating the offset and filling the DSOAndOffset data structure. |
Also, we are going to do a massive sync this quarter, so this problem will be fixed. |
Ok. |
Quipper give AutoFDO sample's file_offset and AutoFDO simply think this file_offset belongs to first load section. It could be fix like:https://github.com/google/autofdo/blob/master/perfdata_reader.cc#L406C1-L411C4. |
In 54991ff, remove checking about "requires the first loadable segment to be executable".
If first loadable segment isn't RE. It's bad to transfer runtime address to binary address.
Why autofdo doesn't use propeller's code about runtime address to binary address?https://github.com/google/autofdo/blob/master/perfdata_reader.cc#L386C2-L395C56
The text was updated successfully, but these errors were encountered: