<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:10.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">Hi Mike,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">This would be a topic that it would be good to get your feedback on. It seems there are various views on whether or not hex input for strtod* functions is required by IEC 60559 or not.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#212121">Regards,<br>
<br>
<b>Rajan Bhakta</b><br>
z/OS XL C/C++ Compiler Technical Architect<br>
ISO C Standards Representative (Canada, USA), PL22.11 Chair<br>
C/C++ Compiler Development</span><span style="color:#212121"><o:p></o:p></span></p>
<p class="MsoNormal"><a href="mailto:rbhakta@us.ibm.com"><span style="font-size:11.0pt;color:#0078D7">rbhakta@us.ibm.com</span></a><span style="color:#212121"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#212121"> </span><span style="color:#212121"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#212121">IBM</span><span style="color:#212121"><o:p></o:p></span></p>
</div>
</div>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">Cfp-interest <cfp-interest-bounces@oakapple.net> on behalf of Jim Thomas <jaswthomas@sbcglobal.net><br>
<b>Date: </b>Monday, January 30, 2023 at 12:00 AM<br>
<b>To: </b>CFP <cfp-interest@ucbtest.org><br>
<b>Cc: </b>Joseph Myers <joseph@codesourcery.com><br>
<b>Subject: </b>[EXTERNAL] [Cfp-interest 2649] Re: GB-287<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">IEEE 754 requires correctly rounded conversions between all supported formats (arithmetic and non-arithmetic). Adding the hexadecimal support completed the required conversions. See H.4.3 and the example in
H.12.2.<br>
<br>
- Jim Thomas<br>
<br>
> On Jan 29, 2023, at 8:32 PM, Fred J. Tydeman <tydeman@tybor.com> wrote:<br>
> <br>
> On Sun, 29 Jan 2023 16:22:18 -0800 Jim Thomas wrote:<br>
>> <br>
>> This note suggests changes requested by WG 14 for response to NB comments GB-286 and GB-287. This note is a draft, for review and discussion at the 2023-01-31 CFP meeting.<br>
>> <br>
>> </span><a href="https://wiki.edg.com/pub/CFP/WebHome/WG14_issues_with_response_to_NB_comments-20230129.pdf"><span style="font-size:11.0pt">https://wiki.edg.com/pub/CFP/WebHome/WG14_issues_with_response_to_NB_comments-20230129.pdf</span></a><span style="font-size:11.0pt">
<br>
> <br>
> <br>
> After rereading IEEE-754-2019, I find that there is NO requirement for conversions<br>
> between hexadecimal strings and decimal floating-point objects.<br>
> <br>
> Therefore, I would suggest that we leave 7.24.1.6 strtodN() family alone (hex is not valid).<br>
> And, we change the Annex H.12.2 strtodN() family to also treat hex as invalid.<br>
> <br>
> <br>
> ---<br>
> Fred J. Tydeman Tydeman Consulting<br>
> tydeman@tybor.com Testing, numerics, programming<br>
> +1 (702) 608-6093 Vice-chair of INCITS/C (ANSI "C")<br>
> Sample C17+FPCE tests: </span><a href="http://www.tybor.com"><span style="font-size:11.0pt">http://www.tybor.com</span></a><span style="font-size:11.0pt">
<br>
> Savers sleep well, investors eat well, spenders work forever.<br>
<br>
<br>
_______________________________________________<br>
Cfp-interest mailing list<br>
Cfp-interest@oakapple.net<br>
</span><a href="http://mailman.oakapple.net/mailman/listinfo/cfp-interest"><span style="font-size:11.0pt">http://mailman.oakapple.net/mailman/listinfo/cfp-interest</span></a><span style="font-size:11.0pt">
<o:p></o:p></span></p>
</div>
</div>
</body>
</html>