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

Directory: fixed X-state leakage from RRIP meta SRAM without reset #163

Merged
merged 2 commits into from
May 21, 2024

Conversation

Kumonda221-CrO3
Copy link
Contributor

@Kumonda221-CrO3 Kumonda221-CrO3 commented May 20, 2024

  • To fix the X-state leakage for accurate quad-state simulation
  • The original code SHOULD WORK without reset in ASIC-only senario
  • The original code SHOULD WORK without reset in non-quad-state, typically dual-state simulation platform (e.g. verilator)
  • The original code SHOULD WORK without reset in quad-state simulation platform if SRAMTemplate able to emit randomized data in non-reset state (not cutting off all X, Z states in simulation procedure and considering only the implementation of SRAMTemplate)
  • The necessity of the reset procedure of RRIP meta SRAM needed to be disscussed
  • The necessity of the utilization of SRAM for single-bit RRIP meta 'origin_bit_opt' and other narrow-bit meta fields needed to be discussed

@Kumonda221-CrO3 Kumonda221-CrO3 added the question Further information is requested label May 20, 2024
@linjuanZ linjuanZ requested a review from Ivyfeather as a code owner May 21, 2024 03:53
@Kumonda221-CrO3 Kumonda221-CrO3 removed the question Further information is requested label May 21, 2024
@Ivyfeather Ivyfeather merged commit ea7d4bd into master May 21, 2024
1 check passed
@Ivyfeather Ivyfeather deleted the fix-rrip-reset branch May 21, 2024 04:38
Ma-YX pushed a commit that referenced this pull request May 24, 2024
)

* Directory: fixed X-state leakage from RRIP meta SRAM without reset

* .github: update CODEOWNERS

---------

Co-authored-by: zhanglinjuan <[email protected]>
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.

5 participants