-
Notifications
You must be signed in to change notification settings - Fork 11.8k
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
[BOLT] assertion failure: "fragment of non-simple function should also be non-simple" #112837
Labels
Comments
@llvm/issue-subscribers-bolt Author: sinan (linsinan1995)
Many checks in BOLT only update the parent functions to non-simple, leaving their fragment status unchanged. This might trigger an assertion failure: "fragment of non-simple function should also be non-simple" in BinaryFunction::getOutputAddressRanges.
|
We could remove this assertion(since it looks like it is being allowed if there are no indirect branches to fragments) or add all non-simple BF with fragments to addFragmentsToSkip. Here is a reduced case for this assertion fail (
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Many checks in BOLT only update the parent functions to non-simple, leaving their fragment status unchanged. This might trigger an assertion failure: "fragment of non-simple function should also be non-simple" in BinaryFunction::getOutputAddressRanges.
The text was updated successfully, but these errors were encountered: