Skip to content
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

Open
lifengxiang1025 opened this issue Jun 27, 2023 · 5 comments

Comments

@lifengxiang1025
Copy link

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

@PandaBlueYellow
Copy link

"Why autofdo doesn't use propeller's code about runtime address to binary address?"
Where is autofdo's current code for handling this logic?

@shenhanc78
Copy link
Collaborator

"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.

Where is autofdo's current code for handling this logic?

perf_data_converter, which is included in AutoFDO as a submodule, is responsible for calculating the offset and filling the DSOAndOffset data structure.

@shenhanc78
Copy link
Collaborator

Also, we are going to do a massive sync this quarter, so this problem will be fixed.

@lifengxiang1025
Copy link
Author

Also, we are going to do a massive sync this quarter, so this problem will be fixed.

Ok.

@lifengxiang1025
Copy link
Author

Where is autofdo's current code for handling this logic?

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants