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.

Sign up for GitHub

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

Jump to bottom

Simplify MEPCC / MTCC legalisation #30

Closed
rmn30 opened this issue Jan 26, 2024 · 2 comments
Closed

Simplify MEPCC / MTCC legalisation #30

rmn30 opened this issue Jan 26, 2024 · 2 comments

Comments

@rmn30
Copy link
Collaborator

rmn30 commented Jan 26, 2024

We could legalize these on write by clearing the tag if relevant bottom bits are set.
@vmurali
Copy link
Collaborator

vmurali commented Jan 26, 2024

+1

rmn30 pushed a commit that referenced this issue Feb 19, 2024
@ronorton
Remove bounds checks on jumps / branch. Simplify and clarify MEPCC an…
c501bb5 
…d MTCC behaviour.

As per #23 we want to delay the bounds check on jumps / branches until instruction
fetch in order to simplify hardware. Due to this potentially leading to
unrepresentable MEPCC values we also clear the tag of MEPCC on instruction fetch
bounds violations. Due to this this got a bit mixed up with #30 which clarifies
and simplifies validation and legalization of MEPCC / MTCC.
@rmn30 rmn30 mentioned this issue Feb 19, 2024
Merged
rmn30 pushed a commit that referenced this issue Feb 19, 2024
@ronorton
Remove bounds checks on jumps / branch. Simplify and clarify MEPCC an…
bec309a 
…d MTCC behaviour.

As per #23 we want to delay the bounds check on jumps / branches until instruction
fetch in order to simplify hardware. Due to this potentially leading to
unrepresentable MEPCC values we also clear the tag of MEPCC on instruction fetch
bounds violations. Due to this this got a bit mixed up with #30 which clarifies
and simplifies validation and legalization of MEPCC / MTCC.
rmn30 pushed a commit that referenced this issue Feb 19, 2024
@ronorton
Remove bounds checks on jumps / branch. Simplify and clarify MEPCC an…
8eeb926 
…d MTCC behaviour.

As per #23 we want to delay the bounds check on jumps / branches until instruction
fetch in order to simplify hardware. Due to this potentially leading to
unrepresentable MEPCC values we also clear the tag of MEPCC on instruction fetch
bounds violations. Due to this this got a bit mixed up with #30 which clarifies
and simplifies validation and legalization of MEPCC / MTCC.
rmn30 pushed a commit that referenced this issue Feb 23, 2024
@ronorton @rmn30
Remove bounds checks on jumps / branch. Simplify and clarify MEPCC an…
0185917 
…d MTCC behaviour.

As per #23 we want to delay the bounds check on jumps / branches until instruction
fetch in order to simplify hardware. Due to this potentially leading to
unrepresentable MEPCC values we also clear the tag of MEPCC on instruction fetch
bounds violations. Due to this this got a bit mixed up with #30 which clarifies
and simplifies validation and legalization of MEPCC / MTCC.
@rmn30
Copy link
Collaborator Author

rmn30 commented Feb 29, 2024

Closing due to #37 being merged.

@rmn30 rmn30 closed this as completed Feb 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@vmurali @rmn30