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
Make BOLT as stable feature #101525
Labels
Comments
I am analyzing several effects of BOLT. |
Need to update get_build_info for the BOLT binary. |
Consider a way to detect post-bolted binary: llvm/llvm-project#60253 |
corona10
added a commit
to corona10/cpython
that referenced
this issue
Apr 2, 2023
corona10
added a commit
that referenced
this issue
Apr 5, 2023
Co-authored-by: Dong-hee Na <donghee.na@linecorp.com>
gaogaotiantian
pushed a commit
to gaogaotiantian/cpython
that referenced
this issue
Apr 8, 2023
…ngh-103187) Co-authored-by: Dong-hee Na <donghee.na@linecorp.com>
warsaw
pushed a commit
to warsaw/cpython
that referenced
this issue
Apr 11, 2023
…ngh-103187) Co-authored-by: Dong-hee Na <donghee.na@linecorp.com>
corona10
added a commit
to corona10/cpython
that referenced
this issue
Apr 16, 2023
corona10
added a commit
that referenced
this issue
Apr 17, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Using a BOLT still not guarantee the unexpected behavior changes.
For example, I observed that #53093 is raised if the binary is optimized by BOLT.
We can reduce several too aggressive optimization.
make test
to work correctly (Should skip the BOLT phase if the binary is already BOLTed)cc @aaupov
Linked PRs
The text was updated successfully, but these errors were encountered: