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

hazards need work #400

Open
davidharrishmc opened this issue Jan 12, 2025 · 0 comments
Open

hazards need work #400

davidharrishmc opened this issue Jan 12, 2025 · 0 comments

Comments

@davidharrishmc
Copy link
Collaborator

davidharrishmc commented Jan 12, 2025

Hazard coverage is missing for various instructions DONE
testgen.py hazard logic uses unusual features and is hard to read/maintain NOT DOING
Can we use the instruction type in the testplan .csv rather than making tables in testgen.py? NOT DOING
Hazards need to generate signature code PENDING
Many hazards have three tests, the third doesn't do anything interesting LIVE WITH IT
Why do branches have waw hazards? They don't seem to do anything. HAMZA IMPROVING COVERPOINTS 2/4/25

# Testcase cp_gpr/fpr_hazard waw test
add x13, x2, x20 # perform first operation
bne x18, x6, arbitraryLabel67
nop
arbitraryLabel67:
nop
 # perform second (triggering) operation

Why do stores have waw hazards?

# Testcase cp_gpr/fpr_hazard waw test
la x26, scratch
addi x26, x26, -1529
add x1, x1, x0 # perform first operation
sw x2, 1529(x26) # perform second (triggering) operation

Store war hazards don't seem to do anything

# Testcase cp_gpr/fpr_hazard war test
la x16, scratch
addi x16, x16, 167
add x31, x10, x21 # perform first operation
sw x5, -167(x16) # perform second (triggering) operation
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

1 participant