<span style=" font-size:10pt;font-family:sans-serif">2019/05/21: 10:00
CST:</span><br><span style=" font-size:10pt;font-family:sans-serif"> <b>Attendees</b>:
Rajan, Jim, Mike, Blaine, David H, </span><br><br><span style=" font-size:10pt;font-family:sans-serif"><b> New
agenda items:</b></span><br><span style=" font-size:10pt;font-family:sans-serif">
None.</span><br><br><span style=" font-size:10pt;font-family:sans-serif"><b> Carry
over action items:</b></span><br><span style=" font-size:10pt;font-family:sans-serif">
All: Review the rationale for part 5 a, b, c proposal. - Carry over.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Fred: Create papers for the SNAN initialization and unary + operation as
CFP papers (CFP 1249, 1253, 1247, 1250) for future submission to WG14.
- Carry over.</span><br><span style=" font-size:10pt;font-family:sans-serif">
</span><br><span style=" font-size:10pt;font-family:sans-serif"><b> Last
meeting action items:</b></span><br><span style=" font-size:10pt;font-family:sans-serif">
Ian: Forward message from Hubert about FLT_EVAL_METHOD, etc. - Done.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Post the IEEE 2019 draft for the CFP group on the wiki. - Done (see
4/25 note).</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Ensure that the quantum exponents table defines dN sufficiently in
C2X. - Carry over (review next draft).</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Get an N number for CFP1277 and submit it. - Done.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Get an N number for CFP1282 as a proposal and submit it. - Done (CFP
review).</span><br><span style=" font-size:10pt;font-family:sans-serif"> </span><br><span style=" font-size:10pt;font-family:sans-serif"><b> New
action items:</b></span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Investigate creating our own CFP compendium.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Fred: Give a new version of the SNAN initialization paper (as per CFP1316).</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Point out to Jens that we're using two spellings for analog in the
current C2X draft.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Look into the commas needed in the why_no_wide_string_strfrom_functions
document, then get a document number and submit it.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Keep Rounding of negated constants on the agenda to discuss for next
meeting.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Keep fesetexcept on the agenda to discuss for next meeting when Fred
is present.</span><br><span style=" font-size:10pt;font-family:sans-serif">
</span><br><span style=" font-size:10pt;font-family:sans-serif"><b> Next
Meeting(s):</b></span><br><span style=" font-size:10pt;font-family:sans-serif">
Wednesday, June 26th, 2019, 11:00 EST, 8:00 PST, 4PM UTC</span><br><span style=" font-size:10pt;font-family:sans-serif">
Same teleconference number.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Please notify the group if this time slot does not work (note the new day).</span><br><br><span style=" font-size:10pt;font-family:sans-serif"><b> Discussion:</b></span><br><span style=" font-size:10pt;font-family:sans-serif">
754 revision:</span><br><span style=" font-size:10pt;font-family:sans-serif">
See CFP 1317.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Draft 50 is the technical content that will go forward.</span><br><span style=" font-size:10pt;font-family:sans-serif">
</span><br><span style=" font-size:10pt;font-family:sans-serif">
C++ Liaison:</span><br><span style=" font-size:10pt;font-family:sans-serif">
None.</span><br><br><span style=" font-size:10pt;font-family:sans-serif">
WG14 meeting (April 29th-May 3rd):</span><br><span style=" font-size:10pt;font-family:sans-serif">
CR process going forward, with Blaine Garst.</span><br><span style=" font-size:10pt;font-family:sans-serif">
See CFP 1318 (Blaine’s email forwarded by Jim).</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: The review cycle is not too short. It is good. Also
us taking over the the compendium is reasonable. A lot of what we had is
in C2X, so any changes to parts 1-4a will go through the C2X process. Our
compendium will be very small now. I liked the meeting history in the original
compendium. I will keep that.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Currently CR's come with some suggested change, rather
than questions.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Blaine: We're not clear yet as a committee. I don't think
the compendium should carry normative content forward. The editors can
make the changes directly. Still need to work out the process.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: I currently put changes into my editors draft as soon
as we have a CR/DR. Nothing goes out until it is closed.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Mike: Often have to go back and make changes to text people
want in immediately.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Blaine: Having the committee agree to the words makes this
much easier.</span><br><span style=" font-size:10pt;font-family:sans-serif">
*AI*: Jim: Investigate creating our own CFP compendium.</span><br><br><span style=" font-size:10pt;font-family:sans-serif">
See CFP 1309.</span><br><span style=" font-size:10pt;font-family:sans-serif">
N2323 will have a new N document (N2379) that doesn't talk
about operations which was what was voted in as direction.</span><br><span style=" font-size:10pt;font-family:sans-serif">
N2326: Jim: I think there is a blurring of value and representation.
Instead of normalized it should be normal number. It has a value of some
normalized form in the model. I think this needs some more thought.</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><br><span style=" font-size:10pt;font-family:sans-serif">
Part 1 – Integration completed.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Part 2 – Integration mostly done.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Part 3 – Expecting N2342 is sufficient for the WG14 editors.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Part 4a – We need to work on something to give to the WG14 editors
for integration into C2X.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Part 5a,b,c,d – Considering new proposals for a,b,c</span><br><br><span style=" font-size:10pt;font-family:sans-serif"> Action
item details:</span><br><span style=" font-size:10pt;font-family:sans-serif">
Fred: Create papers for the SNAN initialization and unary + operation as
CFP papers (CFP 1249, 1253, 1247, 1250) for future submission to WG14.</span><br><span style=" font-size:10pt;font-family:sans-serif">
See Tydeman’s CFP 1290. Jim’s CFP 1316.</span><br><span style=" font-size:10pt;font-family:sans-serif">
*AI*: Fred: Give a new version of the SNAN initialization paper
(as per CFP1316).</span><br><br><span style=" font-size:10pt;font-family:sans-serif">
All: Review the rationale for part 5 a, b, c proposal.</span><br><span style=" font-size:10pt;font-family:sans-serif">
</span><a href=http://wiki.edg.com/pub/CFP/WebHome/n2120.pdf><span style=" font-size:10pt;color:blue;font-family:sans-serif">http://wiki.edg.com/pub/CFP/WebHome/n2120.pdf</span></a><span style=" font-size:10pt;font-family:sans-serif">,
</span><a href=http://wiki.edg.com/pub/CFP/WebHome/n2121.pdf><span style=" font-size:10pt;color:blue;font-family:sans-serif">http://wiki.edg.com/pub/CFP/WebHome/n2121.pdf</span></a><span style=" font-size:10pt;font-family:sans-serif">,
</span><a href=http://wiki.edg.com/pub/CFP/WebHome/n2122.pdf><span style=" font-size:10pt;color:blue;font-family:sans-serif">http://wiki.edg.com/pub/CFP/WebHome/n2122.pdf</span></a><br><br><span style=" font-size:10pt;font-family:sans-serif">
Ian: Forward message from Hubert about FLT_EVAL_METHOD, etc. See Ian’s
CFP 1287.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Seems C++ takes C FLT_EVAL_METHOD.</span><br><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Ensure that the quantum exponents table defines dN sufficiently in
C2X.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Jens wanted to use or refer to the macros in tgmath, and I
wanted to avoid referring to tgmath. This will be an item for the next
meeting.</span><br><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Get an N number for CFP1277 and submit it.</span><br><span style=" font-size:10pt;font-family:sans-serif">
</span><a href=http://wiki.edg.com/pub/CFP/WebHome/n2384.pdf><span style=" font-size:10pt;color:blue;font-family:sans-serif">http://wiki.edg.com/pub/CFP/WebHome/n2384.pdf</span></a><br><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Get an N number for CFP1282 as a proposal and submit it (possibly
after CFP review?).</span><br><span style=" font-size:10pt;font-family:sans-serif">
</span><a href="http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-"><span style=" font-size:10pt;color:blue;font-family:sans-serif">http://wiki.edg.com/pub/CFP/WebHome/C2x_proposal_-</span></a><span style=" font-size:10pt;font-family:sans-serif">_why_no_wide_string_strfrom_functions.pdf</span><br><span style=" font-size:10pt;font-family:sans-serif">
Mike: Slight editorial comment: Should avoid spellings that have
one side identical to the other.</span><br><span style=" font-size:10pt;font-family:sans-serif">
*AI*: Point out to Jens that we're using two spellings for analog
in the current C2X draft.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Mike: Should be a comma after the etc. at the end too.</span><br><span style=" font-size:10pt;font-family:sans-serif">
*AI*: Jim: Look into the commas needed in the why_no_wide_string_strfrom_functions
document.</span><br><br><span style=" font-size:10pt;font-family:sans-serif"> Other issues</span><br><span style=" font-size:10pt;font-family:sans-serif">
Rounding of negated floating-point constants under FENV_ROUND pragma.</span><br><span style=" font-size:10pt;font-family:sans-serif">
See Jim’s CFP 1314 and Mike’s 5/14 reply.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Same issue if you add more digits to the constant.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Mike: Not really.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: In C the negation is an operator, not part of the constant.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Matters for +inf or -inf rounding, which is different from what
strtod or scarf would do.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Mike: They would have to know but programmers do have a choice with
this.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Could be done with parenthesis around the constant too.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Mike: It is an issue for unary + as well.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: It shouldn't be. This is only for unary -.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: C doesn't have any way of representing negative values as a
constant.</span><br><span style=" font-size:10pt;font-family:sans-serif">
*AI*: Jim: Keep Rounding of negated constants on the agenda to discuss
for next meeting.</span><br><br><span style=" font-size:10pt;font-family:sans-serif">
fesetexcept and optional inexact</span><br><span style=" font-size:10pt;font-family:sans-serif">
See CFP email thread “fesetexcept() and optional inexact”</span><br><span style=" font-size:10pt;font-family:sans-serif">
*AI*: Jim: Keep fesetexcept on the agenda to discuss for next meeting
when Fred is present.</span><br><br><span style=" font-size:10pt;font-family:sans-serif">
Fred’s WG 14 papers:</span><br><span style=" font-size:10pt;font-family:sans-serif">
See WG14 email thread “N2380: printf of NaN()”</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: The sign of the NaN is also not portable across implementations.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Mike: This sounds like the most non-problem I can think of.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Existing portable code already has to deal with this along
with all other implementation defined behavior.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: 60559 has payloads being implementation specific. No goal of
making them portable, the opposite in fact.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Mike/Rajan: This can be done portably now with output to a sprintf
buffer and processing the NaN string.</span><br><span style=" font-size:10pt;font-family:sans-serif">
</span><BR>