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

Doubt on definedBy #18

Closed
AFOliveira opened this issue Aug 19, 2024 · 1 comment
Closed

Doubt on definedBy #18

AFOliveira opened this issue Aug 19, 2024 · 1 comment

Comments

@AFOliveira
Copy link
Collaborator

Hello!
While trying to achieve the automatically generated .yaml filesm I found something that raised a doubt.

In the following image:
image
the instruction andn is "defined by: B and Zbb" although Zbb is a part of "B". Isn't this redundant?

The problem I find with this when automatic generating it is that on riscv-opcodes , folder name is zbb and so on my approach, it only shows up zbb. I wanted to hear back from you whether you think it is important to have both, since as of now, only zbb is being parsed on this initial approach.

@dhower-qc
Copy link
Collaborator

As we discussed on the side, the current issue is that if we omit B from the above definition, the tool has no way to associate andn with the B extension. This is because the description of the B extension points to Zbb (the 'implies' key), but Zbb doesn't point back to B.

I am going to look at restructuring the schema so that we can determine Zbb is a subset of B. If we have that, we can omit B from definedBy above.

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