-
Notifications
You must be signed in to change notification settings - Fork 171
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
PHI nodes not grouped at top of basic block! #779
Comments
zoecarver
added a commit
to zoecarver/souper
that referenced
this issue
Oct 6, 2020
If replacing a PHI node with another instruction, make sure the insertion point is after the last PHI node in that block. This prevents the assertion described in google#779.
zoecarver
added a commit
to zoecarver/souper
that referenced
this issue
Oct 6, 2020
If replacing a PHI node with another instruction, make sure the insertion point is after the last PHI node in that block. This prevents the assertion described in google#779.
zoecarver
added a commit
to zoecarver/souper
that referenced
this issue
Oct 7, 2020
If replacing a PHI node with another instruction, make sure the insertion point is after the last PHI node in that block. This prevents the assertion described in google#779.
zoecarver
added a commit
to zoecarver/souper
that referenced
this issue
Oct 9, 2020
If replacing a PHI node with another instruction, make sure the insertion point is after the last PHI node in that block. This prevents the assertion described in google#779.
regehr
pushed a commit
that referenced
this issue
Oct 16, 2020
If replacing a PHI node with another instruction, make sure the insertion point is after the last PHI node in that block. This prevents the assertion described in #779.
Jacarte
pushed a commit
to KTH/souper
that referenced
this issue
Dec 21, 2020
If replacing a PHI node with another instruction, make sure the insertion point is after the last PHI node in that block. This prevents the assertion described in google#779.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
compiled like this:
ends up with:
The text was updated successfully, but these errors were encountered: