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

sve_merge_store_data doesn't account for source vector elements and destination memory elements being different widths #360

Closed
jj16791 opened this issue Dec 16, 2023 · 0 comments · Fixed by #363
Assignees
Labels
0.9.6 Part of SimEng Release 0.9.6 bug Something isn't working

Comments

@jj16791
Copy link
Contributor

jj16791 commented Dec 16, 2023

sve_merge_store_data assumes its to-be-stored data and the memory access are the same width. This is false with one incorrectly implemented example being the st1w {zt.d}, pg, [zn.d{, #imm}] where the source vector elements are of width 64bits whilst the memory elements to be stored are of width 32bits.

@jj16791 jj16791 added the bug Something isn't working label Dec 16, 2023
@jj16791 jj16791 self-assigned this Dec 16, 2023
@jj16791 jj16791 linked a pull request Dec 16, 2023 that will close this issue
@jj16791 jj16791 moved this from ToDo to In Review in SimEng Development Dec 16, 2023
@FinnWilkinson FinnWilkinson added the 0.9.6 Part of SimEng Release 0.9.6 label Dec 16, 2023
@github-project-automation github-project-automation bot moved this from In Review to Done in SimEng Development Dec 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0.9.6 Part of SimEng Release 0.9.6 bug Something isn't working
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants