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

Add a table comparing RVA and RVB #179

Closed
wants to merge 1 commit into from
Closed

Add a table comparing RVA and RVB #179

wants to merge 1 commit into from

Conversation

rpsene
Copy link
Contributor

@rpsene rpsene commented Aug 21, 2024

This update enhances the documentation by providing a clear and organized comparison of the RVA and RVB extensions, making it easier for developers and stakeholders to understand the differences and requirements.

  • Added a new table to the documentation that provides a detailed comparison between the RVA23U64, RVA23S64, RVB23U64, and RVB23S64 extensions.
  • Sorted the entries alphabetically and updated the numbering for clarity and consistency.

@rpsene
Copy link
Contributor Author

rpsene commented Aug 21, 2024

@kasanovic @aswaterman please, double check each line. I did went thorough rva and and rvb multiple times, but I'm not 100% confident that I captured it precisely.

@rpsene rpsene force-pushed the main branch 2 times, most recently from 5620edf to 831feb6 Compare August 21, 2024 18:39
@james-ball-qualcomm
Copy link

Can we add another view of this information that just shows the differences between RVA23 and RVB23? I still want this even though they are split into 2 separate OpaVotes.

@aswaterman
Copy link
Member

RVA and RVB are really separate beasts, and so linking them together in the form of a table doesn’t make much sense to me. I’ll scan the table for fact-checking purposes, but I won’t be the one to approve the PR.

@james-ball-qualcomm
Copy link

I'm asking for another view of the table that omits rows that are the same between RVA23 and RVB23. Make sense?

@james-ball-qualcomm
Copy link

I don't care if it gets approved in a pull request. I just want to see the information.

@aswaterman
Copy link
Member

The only bugs I spotted in the table are that Zicond and Zcmop are missing.

@james-ball-qualcomm
Copy link

I don't see the H extension (mandatory in RVA23, expansion option in RVB23) mentioned. Also, when H is present, there are several other extensions like Ssstateen, Shcounterenw, etc. that become mandatory but I don't see those mentioned in the table either.

@rpsene
Copy link
Contributor Author

rpsene commented Aug 21, 2024

@james-ball-qualcomm H and its dependencies are on the table.

image

@james-ball-qualcomm
Copy link

I don't see H or its friends in the table sent out by Jeff about an hour ago. Is his table incorrect/incomplete/out-of-date?

Screenshot 2024-08-21 165126
RVA23 vs RVB23 Differences.pdf

@rpsene
Copy link
Contributor Author

rpsene commented Aug 21, 2024

I don't see H or its friends in the table sent out by Jeff about an hour ago. Is his table incorrect/incomplete/out-of-date?

Screenshot 2024-08-21 165126

RVA23 vs RVB23 Differences.pdf

@james-ball-qualcomm I shared a complete version before the email was sent. If you check the Google Sheet, it is fully updated.

@james-ball-qualcomm
Copy link

I don't see any email from you sharing a complete version before Jeff's email went out. Also, what do you mean the Google Sheet? All I'm aware of is this ASCIIDOC table in this GitHub and then a PDF that Jeff mailed out. Is there also a Google Sheet?

@james-ball-qualcomm
Copy link

I'm sending you a meeting request so we can discuss this live and clear it up quickly.

@aswaterman aswaterman closed this Aug 31, 2024
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.

3 participants