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

Switch Fence.tso to not pseudo #330

Closed

Conversation

AFOliveira
Copy link
Contributor

Just to get complient with the ISA Manual as clarified in riscv/riscv-isa-manual#1782

Signed-off-by: Afonso Oliveira <[email protected]>
Copy link

codecov bot commented Dec 20, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 74.01%. Comparing base (383cbca) to head (8a8b738).
Report is 6 commits behind head on master.

❗ There is a different number of reports uploaded between BASE (383cbca) and HEAD (8a8b738). Click for more details.

HEAD has 5 uploads less than BASE
Flag BASE (383cbca) HEAD (8a8b738)
10 5
Additional details and impacted files
@@             Coverage Diff             @@
##           master     #330       +/-   ##
===========================================
- Coverage   96.53%   74.01%   -22.52%     
===========================================
  Files          10        3        -7     
  Lines         750      408      -342     
===========================================
- Hits          724      302      -422     
- Misses         26      106       +80     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@AFOliveira
Copy link
Contributor Author

This failed because they overlap (which I guess they should), should I go in the code and make this not an error?

@aswaterman
Copy link
Member

Or just leave it as a pseudo for pragmatic reasons.

@AFOliveira
Copy link
Contributor Author

Or just leave it as a pseudo for pragmatic reasons.

Well, that would definitely be easier :), but can't this be problematic for users of the outputs? I realized that many outputs don't use pseudo, so couldn't it be misleading?

@aswaterman
Copy link
Member

The reason that it isn't problematic in practice is that it is deliberate that the FENCE encoding subsumes the FENCE.TSO encoding: the FENCE encoding is such that, if you ignore the bit that distinguishes FENCE.TSO from FENCE, the processor will still do the right thing (but in a slightly more conservative fashion).

So I don't want to spend time solving a problem that need not be solved.

@AFOliveira
Copy link
Contributor Author

I understand, thank you for the clarification @aswaterman.

@AFOliveira AFOliveira closed this Dec 22, 2024
@aswaterman
Copy link
Member

You're welcome, and thanks for playing ball.

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.

2 participants