-
Notifications
You must be signed in to change notification settings - Fork 165
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
Interpretation of floating-point types #430
Comments
cmuellner
added a commit
to cmuellner/riscv-elf-psabi-doc
that referenced
this issue
Jun 25, 2024
As reported in riscv-non-isa#430, we define the sizes and alignments of all floating-point types, but we don't reference the underlying standards. This change fills this gap. Fixes: riscv-non-isa#430. Signed-off-by: Christoph Müllner <christoph.muellner@vrull.eu>
cmuellner
added a commit
to cmuellner/riscv-elf-psabi-doc
that referenced
this issue
Jun 25, 2024
As reported in riscv-non-isa#430, we define the sizes and alignments of all floating-point types, but we don't reference the underlying standards. This change fills this gap. Fixes: riscv-non-isa#430. Signed-off-by: Christoph Müllner <christoph.muellner@vrull.eu>
cmuellner
added a commit
to cmuellner/riscv-elf-psabi-doc
that referenced
this issue
Jun 25, 2024
As reported in riscv-non-isa#430, we define the sizes and alignments of all floating-point types, but we don't reference the underlying standards. This change fills this gap. Fixes: riscv-non-isa#430. Signed-off-by: Christoph Müllner <christoph.muellner@vrull.eu>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The ABI indicates that
float
is 4 bytes anddouble
is 8 bytes, etc., but we do not actually say thatfloat
is IEEE 754 binary32,double
is IEEE 754 binary64, etc.I think this spec is the right place for that, rather than the C API, because it is at least conceivable that alternate RISC-V C APIs supported by different ABIs would be defined that specify e.g.
long double
as an 8-byte type. But I'll leave it to the experts to make that decision.Note that it does not suffice to say that the C implementation conforms to Annex F, because Annex F only specifies
float
anddouble
. It leaves multiple options forlong double
; we want to specifylong double
to be IEEE 754 binary128.The text was updated successfully, but these errors were encountered: