[Cfp-interest] Fw: (SC22WG14.13405) new documents

Rajan Bhakta rbhakta at us.ibm.com
Thu Aug 14 10:58:00 PDT 2014


My proposed response inline prefixed with "*CFP:" below.

If I don't get any responses to the contrary soon, I will send the 
response as is.

Regards,

Rajan Bhakta
z/OS XL C/C++ Compiler Technical Architect
ISO C Standards Representative for Canada
C Compiler Development
Contact: rbhakta at us.ibm.com, Rajan Bhakta/Houston/IBM
----- Forwarded by Rajan Bhakta/Houston/IBM on 08/14/2014 12:45 PM -----

From:   jacob navia <jacob at jacob.remcomp.fr>
To:     WG14 <sc22wg14 at open-std.org>
Date:   08/14/2014 04:34 AM
Subject:        (SC22WG14.13405) new documents
Sent by:        owner-sc22wg14 at open-std.org



Hi everybody

I am implementing the float128 type in my compiler system. I have found 
the document of "Thomas" very useful of course
N1797 2014/03/09 Thomas, Floating-point extensions for C – Part 4: 
Supplementary functions
N1796 2014/03/09 Thomas, Floating-point extensions for C – Part 3: 
Interchange and extended types
but I have some questions:


1) Status. Is this considered as approved or very likely to be approved?

*CFP: Yes, part 3 is currently in PDTS ballot (closing tomorrow I believe) 
with no notification of any comments so far.

2) In the parts 3 and 4 there is NO mention of any printf modifications 
to accomodate the new floatXXX types. How is this supposed to be done?

I am already using the "q" (quad) letter as a modifier for printing the 
float 512 types that I have already implemented. Can it be used as

"q128"
"q256"
"q512"

for formatting those numbers with printf?

*CFP: The intent is to use the strfromfN functions (defined in section 13 
of part 3) instead of using printf directly.

3) Immediate constants
I am using the suffix F128 or f128 for 128 bit numbers and the suffix 
"Q" or "q" for the 512 bits ones.
What would be the recommended practice?

Example:

12345.67890123F128 --> 128 bit float This is planned, not implemented yet
12345.67890123Q --> 512 bit float This is already running (since 2008)

*CFP: The constant suffixes you have are good for 128 bit numbers. For 
512, you would follow the same convention as defined in section 9 of part 
3: F512 or f512. In your example, it would be: 12345.67890123F512.

Thanks in advance

jacob


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.oakapple.net/pipermail/cfp-interest/attachments/20140814/a4917238/attachment.html 


More information about the Cfp-interest mailing list