-
Notifications
You must be signed in to change notification settings - Fork 201
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
ISA Zfinx extension #668
Comments
The easiest way to check this is disassembling the generated code with
riscv32-unknown-elf-objdump -d and check for the float operations.
As you said you can compile twice, so you can make the dump twice and diff
them.
|
It seems that the operations are the same, so I deduce that I haven't activated the zfinx extension properly. |
You need to check first if your toolchain actually supports the Anyway, you can also "force" the compiler to infer |
Thanks for those precision, how can i know if the toolchain support it ? |
Good question 😅 Unfortunately, it is quite hard to make GCC emit a list off all supported Or just try to compile a simple floating-point program with |
I've tried looking, but it seems that my toolchain can't use the Zfinx extension, I'm working with RTEMS and the riscv-rtems6-gcc toolchain. I don't know if this is possible, but I need an answer and another opinion on my conclusion. Other question, does the riscv32-unknown-elf-gcc can use this extension ? |
No, not yet. According to this list https://gcc.gnu.org/gcc-13/changes.html support for the However, you can still utilize this extension with older GCC versions by using intrinsics. |
Thanks a lot for your help !
Yeah thanks for this precision ! It could be helpful. |
Hello,
I'd like to ask you a question. I would like to use the Zfinx ISA extension to perform float calculations.
The only problem is that my code compiles whether I add zfinx to the compile flag or not.
(-march=rv32im_zfinx)
My question is how can I be sure that the float calculations are used by the hardware and not the software?
Thank you in advance for your answers.
The text was updated successfully, but these errors were encountered: