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

Reduce duplicate code between various backend templates #411

Open
wants to merge 38 commits into
base: main
Choose a base branch
from

Conversation

james-ball-qualcomm
Copy link
Collaborator

No description provided.

… updated $ref syntax (matching certificates).
…if a different design was passed to it which seems bizzare since it goes out of its way to support having a different type for different designs. So, I modified it to work like the type cache in ast and do what I think it wanted to do in the first place.
…ke it clearer the return type since I found bugs in the code related to this.
…n't have (i.e. in @config). Also true for implemented and prohibited.
…ns, CSRs, and traps that aren't in the configuration). Still need to fix traps and interrupts.
…o frontend /arch files. And, also igore *.bak files in Git.
… (especially rakefiles). Now use cfg "_" instead of rv32 or rv64 since there really is no difference in the generated design.
@james-ball-qualcomm james-ball-qualcomm linked an issue Jan 10, 2025 that may be closed by this pull request
@james-ball-qualcomm
Copy link
Collaborator Author

Ooops, meant to make this a draft PR.

@james-ball-qualcomm james-ball-qualcomm changed the title Adding missing items to .gitignore Reduce duplicate code between various backend templates Jan 11, 2025
@james-ball-qualcomm
Copy link
Collaborator Author

I'd like to get this merged into main.

@ThinkOpenly
Copy link
Collaborator

Not to be a pain, but it would be nice if each commit was reasonably understandable standalone:

  • a meaningful subject line for the commit message
  • a meaningful description in the body of the commit message

I'm looking at "One more fix" and "Finished" in particular. ;-)

We don't have contribution guidelines, but we probably should start thinking about that. The generations that follow us might need to understand why we made the choices we made. :-)

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.

Reduce duplicate code between various backend templates
2 participants