Skip to content

[SandboxIR] Remove incorrect assertion. #115553

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

Merged
merged 1 commit into from
Nov 8, 2024

Conversation

slackito
Copy link
Collaborator

@slackito slackito commented Nov 8, 2024

insertBefore can be called on a detached instruction, and we can't check that the underlying instructions are ordered because instructions without BB parents have no order.

This problem showed up as a different assertion failure in llvm::Instruction::comesBefore in one of the unit tests when EXPENSIVE_CHECKS are enabled.

insertBefore can be called on a detached instruction, and we can't check
that the underlying instructions are ordered because instructions
without BB parents have no order.

This problem showed up as a different assertion failure in
llvm::Instruction::comesBefore in one of the unit tests when
EXPENSIVE_CHECKS are enabled.
@slackito slackito requested review from vporpo and aeubanks November 8, 2024 22:08
Copy link
Contributor

@vporpo vporpo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LG

@slackito slackito merged commit 7a6a52a into llvm:main Nov 8, 2024
6 of 8 checks passed
@slackito slackito deleted the remove-incorrect-assertion branch November 9, 2024 01:22
Groverkss pushed a commit to iree-org/llvm-project that referenced this pull request Nov 15, 2024
`insertBefore` can be called on a detached instruction, and we can't
check that the underlying instructions are ordered because instructions
without BB parents have no order.

This problem showed up as a different assertion failure in
`llvm::Instruction::comesBefore` in one of the unit tests when
`EXPENSIVE_CHECKS` are enabled.
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

Successfully merging this pull request may close these issues.

2 participants