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.

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

Support REAL$n for all binary$n types in IEEE754 #11

Open
jeffhammond opened this issue Jul 21, 2017 · 0 comments
Open

Support REAL$n for all binary$n types in IEEE754 #11

jeffhammond opened this issue Jul 21, 2017 · 0 comments

Comments

@jeffhammond
Copy link
Member

jeffhammond commented Jul 21, 2017

Change

13.8.2.21 REAL32, REAL64, and REAL128
The values of these default integer scalar named constants shall be those of the kind type parameters that specify a REAL type whose storage size expressed in bits is 32, 64, and 128 respectively. If, for any of these constants, the processor supports more than one kind of that size, it is processor dependent which kind value is provided. If the processor supports no kind of a particular size, that constant shall be equal to -2 if the processor supports kinds of a larger size and -1 otherwise.

to

... REAL16, REAL32, REAL64, REAL128, and REAL256
The values of these default integer scalar named constants shall be those of the kind type parameters that specify a REAL type whose storage size expressed in bits is 16, 32, 64, 128, and 256 respectively. If, for any of these constants, the processor supports more than one kind of that size, it is processor dependent which kind value is provided. If the processor supports no kind of a particular size, that constant shall be equal to -2 if the processor supports kinds of a larger size and -1 otherwise.

These five floating-point types correspond to the five binary types in IEEE754.

My desire for binary16 is much stronger than that of binary256.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant