<span style=" font-size:10pt;font-family:sans-serif">For my AI:</span><br><br><span style=" font-size:10pt;font-family:sans-serif">Fixes to the source:</span><br><span style=" font-size:10pt;font-family:sans-serif">char[n] s; ->
char s[n];</span><br><br><span style=" font-size:10pt;font-family:sans-serif">That results in
the following:</span><br><span style=" font-size:11pt;font-family:Menlo-Regular"> // convert
d to single-byte character string s</span><br><span style=" font-size:11pt;font-family:Menlo-Regular"> char
s[n];</span><br><span style=" font-size:11pt;font-family:Menlo-Regular"> int
nc = strfromd(s, n, "%g", d);</span><br><span style=" font-size:11pt;font-family:Menlo-Regular"> // convert
s (regarded as a multi-byte character string) to wide string ws</span><br><span style=" font-size:11pt;font-family:Menlo-Regular"> (void)mbstowcs(ws,
s, n);</span><br><br><span style=" font-size:10pt;font-family:sans-serif">This compiles
and runs fine on my z/OS and AIX systems using basic english character
encodings (ASCII and EBCDIC-1047).</span><br><br><span style=" font-size:10pt;font-family:sans-serif">Regards,<br><br>Rajan Bhakta<br>z/OS XL C/C++ Compiler Technical Architect<br>ISO C Standards Representative for Canada, PL22.11 Chair (USA)<br>C Compiler Development<br>Contact: rbhakta@us.ibm.com, Rajan Bhakta/Houston/IBM</span><br><br><br><br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">From:
</span><span style=" font-size:9pt;font-family:sans-serif">Jim
Thomas <jaswthomas@sbcglobal.net></span><br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">To:
</span><span style=" font-size:9pt;font-family:sans-serif">CFP
<cfp-interest@ucbtest.org></span><br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Date:
</span><span style=" font-size:9pt;font-family:sans-serif">11/20/2019
06:04 PM</span><br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Subject:
</span><span style=" font-size:9pt;font-family:sans-serif">[EXTERNAL]
[Cfp-interest 1441] WG14 IEEE 754-C binding meeting minutes
2019/11/20</span><br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Sent
by: </span><span style=" font-size:9pt;font-family:sans-serif">cfp-interest-bounces@oakapple.net</span><br><hr noshade><br><br><br><span style=" font-size:10pt;font-family:sans-serif"> <b>Attendees</b>:
Rajan, Fred, Jim, David H, Mike, Ian</span><span style=" font-size:12pt"><br></span><span style=" font-size:10pt;font-family:sans-serif"><b><br> New agenda items:</b><br> Jens email (SC22WG14.17316) WG14 gorvernance </span><span style=" font-size:12pt"><br></span><span style=" font-size:10pt;font-family:sans-serif"><b><br> Carry over action items:</b><br> CFP: Put the tgmath redefinition as a proposal to the standard
once we have a base document with TS Part 3 in it. Carry over again.</span><br><span style=" font-size:10pt;font-family:sans-serif">
<b><br> Last meeting action items:</b><br> CFP: Follow up on CFP1419 via email. DONE<br> Jim: Create a WG14 paper for the next Spring 2020 WG14 meeting
along the lines of CFP1411. DONE</span><br><span style=" font-size:10pt;font-family:sans-serif"><b><br> New action items:</b><br> Fred: Update erange proposal based on CFP 1437 and CFP teleconference
discussion.<br> Jim: Submit </span><a href="http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-_NaN_and_infinity_macros_-_20191108.pdf"><span style=" font-size:10pt;color:blue;font-family:sans-serif"><u>http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-_NaN_and_infinity_macros_-_20191108.pdf</u></span></a><span style=" font-size:10pt;font-family:sans-serif">to WG14</span><span style=" font-size:12pt;font-family:sans-serif">.</span><br><span style=" font-size:12pt;font-family:sans-serif">
Rajan: Compile example code in </span><a href="http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-_why_no_wide_string_strfrom_functions_v2.pdf"><span style=" font-size:10pt;color:blue;font-family:sans-serif"><u>http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-_why_no_wide_string_strfrom_functions_v2.pdf</u></span></a><span style=" font-size:12pt;font-family:sans-serif">.</span><br><span style=" font-size:12pt;font-family:sans-serif">
Jim: Choose how to attach footnote in </span><a href="http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-_why_no_wide_string_strfrom_functions_v2.pdf"><span style=" font-size:10pt;color:blue;font-family:sans-serif"><u>http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-_why_no_wide_string_strfrom_functions_v2.pdf</u></span></a><span style=" font-size:10pt;font-family:sans-serif">;
mention the other approach in the problem description.</span><br><span style=" font-size:10pt;font-family:sans-serif">
JIm: Draft a paper proposing changing the “cr” prefix for correctly rounded
functions to “cr_”. Include with other suggested changes in response
to Jens’s naming paper.</span><br><span style=" font-size:10pt;font-family:sans-serif">
David H: Draft words to recommend honoring properties of math functions
that would follow automatically from correct rounding.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Find a place for words about math function properties. Coordinate
with David H (previous AI).</span><br><span style=" font-size:12pt;font-family:sans-serif">
Jim: Draft a proposal to change the return words for powr and add the footnote
(presented in the meeting) to justify powr.</span><br><span style=" font-size:10pt;font-family:sans-serif">
<b><br> Next Meeting(s):</b><br> Thursday, January 9th, 2020, 11:00 EST, 8:00 PST, 4PM UTC<br> Same teleconference number.<br> Please notify the group if this time slot does not work.</span><span style=" font-size:12pt"><br></span><span style=" font-size:10pt;font-family:sans-serif"><b><br> Discussion:</b><br> 754 revision:<br> This is the final resting place for the public records
of 754-2019 development, </span><span style=" font-size:10pt;color:blue;font-family:sans-serif"><u><br></u></span><a href="http://grouper.ieee.org/groups/msc/ANSI_IEEE-Std-754-2019"><span style=" font-size:10pt;color:blue;font-family:sans-serif"><u>http://grouper.ieee.org/groups/msc/ANSI_IEEE-Std-754-2019</u></span></a><br><span style=" font-size:10pt;font-family:sans-serif">in the IEEE SA
MSC page.</span><span style=" font-size:10pt;color:blue;font-family:sans-serif"><u><br></u></span><a href="http://grouper.ieee.org/groups/msc/index.html"><span style=" font-size:10pt;color:blue;font-family:sans-serif"><u>http://grouper.ieee.org/groups/msc/index.html</u></span></a><br><span style=" font-size:10pt;font-family:sans-serif"><br> C++ Liaison:<br> Nothing.</span><br><br><span style=" font-size:10pt;font-family:sans-serif">
Jens’s email (SC22WG14.17316) WG14 governance</span><br><span style=" font-size:10pt;font-family:sans-serif">
Discussed content and relevance to CFP.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Concerns about transition to new editor and work in progress.</span><br><span style=" font-size:10pt;font-family:sans-serif"><br> WG14 meeting in Ithaca</span><br><span style=" font-size:10pt;font-family:sans-serif">
See CFP 1432 - Rajan’s report on CFP related issues</span><br><span style=" font-size:10pt;font-family:sans-serif">
Excerpts …</span><br><span style=" font-size:10pt;font-family:sans-serif">Here is a summary
of the results for what was discussed for floating point papers yesterday.
Note that we have one action item (reword N2400), and also the proposal
for Part 5 a and b went a lot better than last time and we got on the verge
of approval (but not quite).</span><br><span style=" font-size:10pt;font-family:sans-serif">
N2384 Thomas, C2X proposal - F.8 update</span><br><span style=" font-size:10pt;font-family:sans-serif">
Goes into C2X.</span><br><span style=" font-size:10pt;font-family:sans-serif">
N2400 Thomas, C2X proposal - why no wide string strfrom functions</span><br><span style=" font-size:10pt;font-family:sans-serif">
CFP to send this text to the editor as a footnote and a recipe
(steps to get wide string version of strfrom code example) form.</span><br><span style=" font-size:10pt;font-family:sans-serif">
N2406 Tydeman, SNAN: initialization and unary +</span><br><span style=" font-size:10pt;font-family:sans-serif">
Goes into C2X.</span><br><span style=" font-size:10pt;font-family:sans-serif">
N2407 Thomas, Proposal for C2X - TS 18661-5abc supplementary attributes</span><br><span style=" font-size:10pt;font-family:sans-serif">
Straw poll: Does the committee want TS 18661-5a to be brought
into C2X?</span><br><span style=" font-size:10pt;font-family:sans-serif">
Result: 5/3/5. Not quite approval.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Straw poll: Does the committee want TS 18661-5b to be brought
into C2X?</span><br><span style=" font-size:10pt;font-family:sans-serif">
Result: 4/3/6. Not approved. </span><br><span style=" font-size:10pt;font-family:sans-serif">
N2416 Thomas, Proposal for C2X - floating-point negation and conversion</span><br><span style=" font-size:10pt;font-family:sans-serif">
Goes into C2X.</span><br><span style=" font-size:10pt;font-family:sans-serif">
N2424 Thomas, Proposal for C2X proposal – Why logp1?</span><br><span style=" font-size:10pt;font-family:sans-serif">
Goes into C2X. </span><br><span style=" font-size:10pt;font-family:sans-serif">
The naming proposal did not pass and there were no action items
for CFP from it. </span><span style=" font-size:12pt;font-family:sans-serif">WG14
didn’t get into the cr prefix or NaN and infinity macro names.</span><br><span style=" font-size:10pt;font-family:sans-serif">
N2409 (reserved names) is something we should track for changes
affecting CFP.</span><br><span style=" font-size:10pt;font-family:sans-serif">
There was no resolution about intmax_t.</span><span style=" font-size:12pt;font-family:sans-serif"> </span><br><span style=" font-size:10pt;font-family:sans-serif"> </span><br><span style=" font-size:10pt;font-family:sans-serif">
C2X integration (</span><a href="http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2433.pdf"><span style=" font-size:10pt;color:blue;font-family:sans-serif"><u>http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2433.pdf</u></span></a><span style=" font-size:10pt;font-family:sans-serif">):<br> Draft includes TS 1, 2, and 4a</span><br><span style=" font-size:10pt;font-family:sans-serif">
TS 5abc inclusion into C2X nearly passed. Might should be resubmitted
later.<br> Part 3 integration status in question, given Jen’s
email.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Too early to update parts not integrated into C2X. Need ISO approval
to republish TS.<br> <b><br> Action item details:</b></span><br><span style=" font-size:10pt;font-family:sans-serif">
CFP: Follow up on CFP1419 via email.<br> See CFP 1437.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Talked through changes proposed in 1437. </span><br><span style=" font-size:10pt;font-family:sans-serif">
Agreed to be consistent on saying “magnitude of”, even if redundant
as in “magnitude of positive finite x is too large. </span><br><span style=" font-size:10pt;font-family:sans-serif">
Agreed to split non-symmetric cases to state positive and negative
cases separately, as in 1437, e.g., in exp and expm1. </span><br><span style=" font-size:10pt;font-family:sans-serif">
Agreed to “A range error occurs for some finite x, depending on
p” for ldexp, and similar words for scalbn and scalbln and elsewhere where
characterization of range errors is complicated. </span><br><span style=" font-size:10pt;font-family:sans-serif">
Agreed to “A range error occurs for some finite arguments” for
fdim. </span><br><span style=" font-size:10pt;font-family:sans-serif">
Agree to avoid “may occur” in general.</span><br><span style=" font-size:10pt;font-family:sans-serif">
*AI*: Fred: Update erange proposal based on CFP 1437 and CFP teleconference
discussion.</span><br><span style=" font-size:10pt;font-family:sans-serif"><br> Jim: Create a WG14 paper for the next Spring 2020 WG14 meeting
along the lines of CFP1411.<br> </span><a href="http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-_NaN_and_infinity_macros_-_20191108.pdf"><span style=" font-size:12pt;color:blue"><u>http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-_NaN_and_infinity_macros_-_20191108.pdf</u></span></a><br><span style=" font-size:10pt;font-family:sans-serif">
Reviewed.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Ok to submit to WG14? Yes.<br> </span><span style=" font-size:12pt;font-family:sans-serif">*AI*:</span><span style=" font-size:10pt;font-family:sans-serif">jJim submit to WG14.</span><br><br><span style=" font-size:10pt;font-family:sans-serif">
</span><span style=" font-size:12pt;font-family:sans-serif">From WG14:</span><br><span style=" font-size:10pt;font-family:sans-serif">
N2400 Thomas, C2X proposal - why no wide string strfrom functions<br> CFP to send this text to the editor as a footnote
and a recipe (steps to get wide string version of strfrom code example)
form. <br> See CFP 1436.</span><br><span style=" font-size:10pt;font-family:sans-serif">
</span><a href="http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-_why_no_wide_string_strfrom_functions_v2.pdf"><span style=" font-size:12pt;color:blue"><u>http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-_why_no_wide_string_strfrom_functions_v2.pdf</u></span></a><br><span style=" font-size:10pt;font-family:sans-serif">
</span><span style=" font-size:12pt;font-family:sans-serif">*AI*:
Rajan: compile code in example.</span><br><span style=" font-size:10pt;font-family:sans-serif">
</span><span style=" font-size:12pt;font-family:sans-serif">*AI*:
Jim: Choose how to attach footnote and </span><span style=" font-size:10pt;font-family:sans-serif">mention
the other approach in the problem description.</span><br><br><span style=" font-size:12pt;font-family:sans-serif"><b> Other
issues:</b></span><br><span style=" font-size:10pt;font-family:sans-serif">
N2426 -- naming issues<br> Shall we propose changing to cr_? Agreed.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Rajan: Include with other changes in response to naming paper.<br> AI: Jim draft a proposal and include other suggested
changes in response to naming paper.</span><br><br><span style=" font-size:10pt;font-family:sans-serif">
Specifying more special cases for math functions, e.g., periodicity for
half-revolution trig functions. Perhaps as recommended practice.<br> Are we going to propose adding anything?<br> Jim: Could there be a note or recommended practice
for implementations to honor function properties that would hold if the
function were correctly rounded, e.g., monotonicity, periodicity, exact
cases, ertc.</span><br><span style=" font-size:10pt;font-family:sans-serif">
*AI*: David H: Draft words to recommend honoring properties of math
functions that would follow automatically with correct rounding.</span><br><span style=" font-size:10pt;font-family:sans-serif">
*AI*: Jim: Find a place for words about math function properties.
Coordinate with David H.</span><br><br><span style=" font-size:10pt;font-family:sans-serif">
powr</span><br><span style=" font-size:10pt;font-family:sans-serif">
Currently says “The powr functions compute x raised to the power
y as e ^ (y log x). …” and “The powr functions return x^y.” </span><br><span style=" font-size:10pt;font-family:sans-serif">
Would it be better to say “The powr functions return e ^ (y log
x).”? Agreed yes.<br> Jens suggested a note about pow vs powr. </span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: How about a footnote attached to the first sentence in the
Description where the footnote is:<br> (*) Restricting the domain to that of the formula
e ^ (y * log(x)) is intended to better meet expectations for a continuous
power function and to allow more efficient implementation by avoiding some
case analysis.</span><br><span style=" font-size:10pt;font-family:sans-serif">
</span><span style=" font-size:12pt;font-family:sans-serif">*AI*:
Jim: draft a proposal to change the return words and add a footnote.</span><span style=" font-size:10pt;font-family:sans-serif"><br><br> Attributes - recent WG14 email thread<br> Does this pertain to CFP?</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: A vehicle for CFP pragma functionality?</span><br><span style=" font-size:10pt;font-family:sans-serif">
Rajan: current ideas are for attributes that don’t apply to blocks,
so no.</span><br><span style=" font-size:10pt;font-family:sans-serif">
</span><br><span style=" font-size:10pt;font-family:sans-serif">
Followup on what does “normalized” mean in C? See CFP 1399<br> Defer.</span><br><br><span style=" font-size:10pt;font-family:sans-serif">- Jim Thomas</span><span style=" font-size:12pt"><br></span><span style=" font-size:10pt;font-family:sans-serif"><br> </span><tt><span style=" font-size:10pt">_______________________________________________<br>Cfp-interest mailing list<br>Cfp-interest@oakapple.net<br></span></tt><a href="http://mailman.oakapple.net/mailman/listinfo/cfp-interest"><tt><span style=" font-size:10pt">http://mailman.oakapple.net/mailman/listinfo/cfp-interest</span></tt></a><tt><span style=" font-size:10pt"><br></span></tt><br><br><BR>