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

About RVA22 zicclsm #202

Open
haosun86 opened this issue Feb 22, 2025 · 4 comments
Open

About RVA22 zicclsm #202

haosun86 opened this issue Feb 22, 2025 · 4 comments

Comments

@haosun86
Copy link

Hi,

In RVA20U64 Mandatory Extensions, zicclsm has the following requirement:

"This introduces a new extension name for this feature. This requires misaligned support for all regular load and store instructions (including scalar and vector) but not AMOs or other specialized forms of memory access. Even though mandated, misaligned loads and stores might execute extremely slowly. Standard software distributions should assume their existence only for correctness, not for performance."

But in RVA22U64 Mandatory Extensions, zicclsm has the following requirement:
"This is a new extension name for this feature. Even though mandated, misaligned loads and stores might execute extremely slowly. Standard software distributions should assume their existence only for correctness, not for performance."

They are inconsistent. RVA22U64 does not describe vector related requirement.
Could you please help explain about the reason?

Thanks
Hao Sun

@aswaterman
Copy link
Member

The snippets you quoted are non-normative, so they shouldn't affect the meaning of the spec. Indeed the normative text simply uses the phrase "misaligned loads and stores", which, absent qualification, implies both scalar and vector.

It probably makes sense to delete the second non-normative note altogether.

@haosun86
Copy link
Author

Okay. Thanks for the explanation.

For vector, I am not sure whether it is necessary to explicitly indicate that the "misaligned" here means element misalign?

Thanks
Hao Sun

@aswaterman
Copy link
Member

The vector spec explains what constitutes a misaligned access in the vector context, so we are relying on that definition. I think that's preferable for separation of concerns.

@haosun86
Copy link
Author

Okay. Thanks a lot.
It is clear.

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

No branches or pull requests

2 participants