-
Notifications
You must be signed in to change notification settings - Fork 643
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
fssr
and frsr
instructions aren't mentioned for F extension
#419
Comments
fssr
and frsr
instructions aren't mentioned for F extensionsfssr
and frsr
instructions aren't mentioned for F extension
They’re pseudoinstructions that map to CSR-access instructions. (And they
may well be missing from the documentation.)
…On Mon, Jul 29, 2019 at 5:19 AM Wladimir J. van der Laan < ***@***.***> wrote:
Just a documentation issue I think: The fssr and frsr instructions (which
set and read the fcsr, respectively) aren't mentioned in the
specification for the F extension. The names don't appear in the spec at
all.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#419?email_source=notifications&email_token=AAH3XQQCEXPROJDOQC7XLXTQB3N4JA5CNFSM4IHR2HOKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HCA6WEQ>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAH3XQS7GCH3ERQGGDI7F3DQB3N4JANCNFSM4IHR2HOA>
.
|
Oh. Thanks! I'm confused now, this came up in rust-embedded/riscv#157, there was the assumption that these were separate instructions, but if they map to the same thing then it's probably not necessary to mention them. |
Hi! I also noticed this issue recently. Are |
Correct. But the obsolete aliases will be supported in perpetuity, since
important software (like glibc) relies upon them.
…On Tue, Jul 30, 2019 at 2:19 AM Mel Chen ***@***.***> wrote:
Hi! I also noticed this issue recently. Are frsr and fssr instructions
obsolete, or renamed to frcsr and fscsr respectively? Thanks.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#419?email_source=notifications&email_token=AAH3XQQPRW5WSYFWLAPOG5TQCABSDA5CNFSM4IHR2HOKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3DLF6Q#issuecomment-516338426>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAH3XQUOEL4MHQS55T3JD5TQCABSDANCNFSM4IHR2HOA>
.
|
Good to know! |
Don't worried. I am preparing binutils patches to update |
Thanks! |
These are just aliases for fscsr and frcsr respectively. They are not mentioned in the specification as they are outdated. They were added because the move.s test uses them. Information about them can be found at riscv/riscv-isa-manual#419
Just a documentation issue I think: The
fssr
andfrsr
instructions (which set and read thefcsr
, respectively) aren't mentioned in the specification for the F extension. The names don't appear in the spec at all.The text was updated successfully, but these errors were encountered: