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

moved upfront the skip branch insertion code for correctness. #21

Closed
wants to merge 1 commit into from
Closed

moved upfront the skip branch insertion code for correctness. #21

wants to merge 1 commit into from

Conversation

cdevadas
Copy link
Collaborator

Moved the skip branch insertion code for correctness from SIInsertSkips into SILowerControlFlow.

@repo-lockdown
Copy link

repo-lockdown bot commented Jul 23, 2019

This repository does not accept pull requests. Please follow http://llvm.org/docs/Contributing.html#how-to-submit-a-patch for contribution to LLVM.

@repo-lockdown repo-lockdown bot closed this Jul 23, 2019
@repo-lockdown repo-lockdown bot locked and limited conversation to collaborators Jul 23, 2019
JordiChauzi referenced this pull request in upmem/llvm-project Aug 5, 2019
This gives numeric names to tuple fields, because lldb clients expect
fields to have names, and because using plain numbers seemed most
rust-like.

Closes #21
artemmukhin pushed a commit to artemmukhin/llvm-project that referenced this pull request Oct 16, 2019
This gives numeric names to tuple fields, because lldb clients expect
fields to have names, and because using plain numbers seemed most
rust-like.

Closes llvm#21
ggreif pushed a commit to ggreif/llvm-project that referenced this pull request Oct 9, 2020
This gives numeric names to tuple fields, because lldb clients expect
fields to have names, and because using plain numbers seemed most
rust-like.

Closes llvm#21

Signed-off-by: Gabor Greif <gabor@dfinity.org>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant