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

[VAN-1370] handle non-scalar function parameters in BucketInterpreter #121

Merged
merged 1 commit into from
Jun 26, 2024

Conversation

tim-hoffman
Copy link

No description provided.

//CHECK-NEXT: %[[T14:[0-9a-zA-Z_.]+]] = mul i32 2, %[[T13]]
//CHECK-NEXT: %[[T15:[0-9a-zA-Z_.]+]] = add i32 %[[T14]], 0
//CHECK-NEXT: %[[T16:[0-9a-zA-Z_.]+]] = getelementptr [0 x i256], [0 x i256]* %lvars, i32 0, i32 %[[T15]]
//CHECK-NEXT: %[[COPY_SRC_0:[0-9a-zA-Z_.]+]] = getelementptr i256, i256* %[[T16]], i32 0
Copy link
Author

Choose a reason for hiding this comment

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

I realize this looks like a regression; what was fixed indexing via a parameter has become dynamic indexing. However, this is actually caused by a different long-standing issue https://veridise.atlassian.net/browse/VAN-671 and the fix to the interpreter has brought it to the surface.

Copy link

@iangneal iangneal left a comment

Choose a reason for hiding this comment

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

LGTM

@tim-hoffman tim-hoffman merged commit 0bc3ca6 into llvm Jun 26, 2024
4 checks passed
@tim-hoffman tim-hoffman deleted the th/VAN-1370 branch June 26, 2024 18:59
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