Skip to content
This repository has been archived by the owner on Mar 20, 2024. It is now read-only.

Does Zvamo imply 'A' extension? #555

Open
Hsiangkai opened this issue Aug 10, 2020 · 3 comments
Open

Does Zvamo imply 'A' extension? #555

Hsiangkai opened this issue Aug 10, 2020 · 3 comments
Labels
Resolve after v1.0 Does not need to be resolved for v1.0 draft toolchain issue

Comments

@Hsiangkai
Copy link
Contributor

If Zvamo implies A extension, rv32i_zvamo is a valid combination. Zvamo will turn on ‘A’ extension implicitly.
If Zvamo does not imply A extension, users need to specify rv32ia_zvamo to support Zvamo.

There is a description about the relationship. “If vector AMO instructions are supported, then the scalar Zaamo instructions (atomic operations from the standard A extension) must be present.” What does it mean “must be present”?

@Nelson1225
Copy link

Nelson1225 commented Aug 13, 2020

The current GNU assembler choose the second one - Zvamo does not imply A extension. But is doesn't mean the current behavior of assembler is right. I'm OK with both (imply or non-imply).

FYI, @kito-cheng reminds me that the ISA spec had the imply list for all extensions [1]. It would be great and helpful if we can also have the similar imply list for vector spec.

[1] https://github.com/riscv/riscv-isa-manual/blob/draft-20200812-1eaebcc/src/naming.tex#L157

Thanks
Nelson

@kasanovic
Copy link
Collaborator

Zvaamo should imply Zaamo rather than entire A, which also includes Zalrsc.

@kasanovic kasanovic added the Resolve after v1.0 Does not need to be resolved for v1.0 draft label Jun 7, 2021
@kasanovic
Copy link
Collaborator

Zvamo is removed from the initial standard vector extensions. These will be added at a later date as a standard extension but need new instruction encodings.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Resolve after v1.0 Does not need to be resolved for v1.0 draft toolchain issue
Projects
None yet
Development

No branches or pull requests

3 participants