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

Clarify note that compilers may need to change vtype for vmv<nr>r.v #1710

Merged
merged 1 commit into from
Nov 4, 2024

Conversation

lukel97
Copy link
Contributor

@lukel97 lukel97 commented Nov 4, 2024

In a similar vein to riscvarchive/riscv-v-spec@856fe5b, this note states that compilers don't need to "know or change vtype" for whole vector register moves.

There's some truth to this in that compilers can largely ignore SEW and LMUL, but ultimately they do depend on vtype and the current wording might be misleading. A compiler may in fact need to change vtype to clear vill, see: llvm/llvm-project#114518

In a similar vein to 856fe5b, this note states that compilers don't
need to "know or change vtype" for whole vector register moves.

There's some truth to this in that compilers can largely ignore SEW
and LMUL, but ultimately they do depend on vtype and the current
wording might be misleading. A compiler may in fact need to change
vtype to clear vill, see:
llvm/llvm-project#114518
Copy link
Member

@aswaterman aswaterman left a comment

Choose a reason for hiding this comment

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

Works for me.

@aswaterman aswaterman merged commit cc636c0 into riscv:main Nov 4, 2024
2 checks passed
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