-
Notifications
You must be signed in to change notification settings - Fork 60
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
WIP: RISC-V standards-compatible subset #2317
base: dev
Are you sure you want to change the base?
Conversation
subrepo: subdir: "contrib/subrepo-cheri-libunwind" merged: "0b81fa00b201" upstream: origin: "https://github.com/CTSRD-CHERI/libunwind.git" branch: "monorepo-mirror" commit: "0b81fa00b201" git-subrepo: version: "0.4.9" origin: "https://github.com/ingydotnet/git-subrepo" commit: "cce3d93"
Still need to remove CHERI_PERM_SEAL/UNSEAL, since that code is no functional
#endif | ||
1: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
switch these?
@@ -474,7 +474,12 @@ ENTRY(cbuildcap_fault) | |||
#else | |||
SET_FAULT_HANDLER(x0, a2) /* Reset the handler function */ | |||
#endif | |||
#if defined(__riscv_xcheri_std_compat) | |||
cgethigh a0, ca1 | |||
csethigh ca0, ca1, a0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we're in standard compat mode, cbuildcap failing is tag-clearing so we shouldn't need this fixup at all? It's to emulate V9 semantics for V8.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah thanks, I was just blindly fixing compiler errors and didn't check what this function was used for.
No description provided.