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

Priv 1.12 ACT - Add Fence Coverage Additions #27

Open
13 tasks
jjscheel opened this issue Apr 6, 2023 · 2 comments
Open
13 tasks

Priv 1.12 ACT - Add Fence Coverage Additions #27

jjscheel opened this issue Apr 6, 2023 · 2 comments
Assignees

Comments

@jjscheel
Copy link
Contributor

jjscheel commented Apr 6, 2023

Technical Group

Applications & Tools HC

ratification-pkg

Priv 1.12

Technical Liaison

Allen Baum

Task Category

Arch Tests

Task Sub Category

  • gcc
  • binutils
  • gdb
  • intrinsics
  • Java
  • KVM
  • ld
  • llvm
  • Linux kernel
  • QEMU
  • Spike

Ratification Target

2020

Statement of Work (SOW)

Component names: RV32/RV64I

Requirements:

Generate tests that use unsupported, legal encodings for Fence and Fencei ops ACT issue 119. Specifically that any reserved bits defined to be ignored do not cause traps.

Note: the standard binutils likelikely cannot generate these opcode, so the .insn assembler directive will need to be used. See
https://sourceware.org/binutils/docs/as/RISC_002dV_002dDirectives.html or https://sourceware.org/binutils/docs-2.34/as/RISC_002dV_002dFormats.html.

Deliverables:

  1. Assembly language tests
  2. Coverage models

Acceptance Criteria:

  1. Assembly language tests that meet the TestFormatSpec
  2. Coverage models using riscv-ctg YAML formatted schema Acceptance criteria
  3. Tests pass using the riscof framework

Projected timeframe: TBD

SOW Signoffs:

  • Task group liaison sign-off date:
  • Development partner sign-off date:
  • ACT SIG sign-off date (if ACT work):

Waiver

  • Freeze
  • Ratification

Pull Request Details

No response

@jjscheel
Copy link
Contributor Author

jjscheel commented Apr 6, 2023

@allenjbaum, I've put your information from your email into this new issue. Please feel free to make any edits you see fit.

Also, if you have a projected need date, we should add that too. (Yes, I recognize this is legacy and "yesterday" my not sound good.)

@allenjbaum
Copy link

This should be a good onboarding project

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Blocked
Development

No branches or pull requests

2 participants