-
Notifications
You must be signed in to change notification settings - Fork 19
feat(located): support ARRAY at a physical address #229
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
Open
JulioSergioFS
wants to merge
2
commits into
development
Choose a base branch
from
feature/gh-565-located-arrays
base: development
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
HIGH — regression: named ARRAY types reach codegen and fail there.
collectLocatedVarpassesdecl.type.arrayDimensions, which isundefinedfor a named ARRAY type, while the analyzer'sresolveLocatedShaperesolves named types throughresolveArrayShapeByName. The two disagree.This passes semantics and correctly reserves 10 slots (a second variable at
%MW65is properly rejected), but codegen emits one descriptor and callsHR.raw_ptr()on an array:On
developmentthe analyzer rejected this cleanly withType 'Buf' is not compatible with address size 'W'. It now fails in the C++ backend leaking internal type names — the exact failure mode this PR set out to remove.The PR's own test
accepts the same shape spelled as a named ARRAY typeonly assertscompile(source).successand has noCONFIGURATION, so codegen's located path is never exercised. Suggest resolving the named type here the same wayresolveLocatedShapedoes, and extending that test with aCONFIGURATIONblock.