<span style=" font-size:10pt;font-family:sans-serif"> <b>Attendees</b>:
Rajan, Jim, Fred (first 20 minutes), David H, Ian, </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. - Done.</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.
- Remove.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Ensure that the quantum exponents table defines dN sufficiently in
C2X. - Done.</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">
Jim: Investigate creating our own CFP compendium. - Done.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Fred: Give a new version of the SNAN initialization paper (as per CFP1316).
- Carry over.</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. - Done.</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. - Done.</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. - Done.</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. - Done.</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: Create a link to the 250 draft into the references section in the
C FP wiki.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Rajan: Forward the IEEE article to WG14 once David H sends it out to us.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Draft a slide deck and a proposal based on CFP1331.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Draft a note to warn about CFP1315's rounding of negative constants
issue.</span><br><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, July 24th, 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.</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">
IEEE standards board approved the 2019 revision. Now will be edited
by the IEEE staff. Should be published this year.</span><br><span style=" font-size:10pt;font-family:sans-serif">
*AI* Jim: Create a link to the 250 draft into the references section
in the C FP wiki.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: When will IEC 60559 be updated and who initiates that?</span><br><span style=" font-size:10pt;font-family:sans-serif">
David H: I don't know. I know it's not us or IEEE. I think they
have to do it.</span><br><span style=" font-size:10pt;font-family:sans-serif">
No one knows of any IEC person.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Fred: David Keaton may.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Will WG14 be willing to consider including the IEEE update
rather than wait for IEC?</span><br><span style=" font-size:10pt;font-family:sans-serif">
Rajan/Fred: They already said they are OK with taking the
new IEEE standard changes for C. No mention on waiting for IEC.</span><br><span style=" font-size:10pt;font-family:sans-serif">
David: Article for IEEE. Maybe interesting to WG14.</span><br><span style=" font-size:10pt;font-family:sans-serif">
*AI* Rajan: Forward the IEEE article to WG14.</span><br><br><span style=" font-size:10pt;font-family:sans-serif">
C++ Liaison:</span><br><span style=" font-size:10pt;font-family:sans-serif">
Ian: Nothing new.</span><br><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 – In C2X (draft </span><a href="http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2385.pdf"><span style=" font-size:10pt;color:blue;font-family:sans-serif">http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2385.pdf</span></a><span style=" font-size:10pt;font-family:sans-serif">)</span><br><span style=" font-size:10pt;font-family:sans-serif">
Part 2 – In C2X.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Part 3 – A draft based on the latest C2X paper is almost ready.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Part 4a – Will be put in first before part 3 to allow part 3 to
be based on that newest working draft with part 4a already integrated in.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Part 4b - Looking as an updated TS.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Part 5a,b,c,d – Discuss later. Part 5d is a TS update.</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">
Jim: Investigate creating our own CFP compendium. See Jim’s CFP 1332.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Looks like a good way forward.</span><br><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.</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">
Leave until next time.</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">
</span><a href="http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2385.pdf"><span style=" font-size:10pt;color:blue;font-family:sans-serif">http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2385.pdf</span></a><br><span style=" font-size:10pt;font-family:sans-serif">
Looks good.</span><br><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">
See </span><a href=http://wiki.edg.com/pub/CFP/WebHome/n2400.pdf><span style=" font-size:10pt;color:blue;font-family:sans-serif">http://wiki.edg.com/pub/CFP/WebHome/n2400.pdf</span></a><span style=" font-size:10pt;font-family:sans-serif">.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Looks good.</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/cfp5x-20180624.pdf"><span style=" font-size:10pt;color:blue;font-family:sans-serif">http://wiki.edg.com/pub/CFP/WebHome/cfp5x-20180624.pdf</span></a><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><br><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><br><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><span style=" font-size:10pt;font-family:sans-serif">
See Jim’s CFP 1331.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Has anything changed so we could repurpose this as a package?</span><br><span style=" font-size:10pt;font-family:sans-serif">
Rajan/David H: I don't think anything has changed.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: The listed low quality implementation is the only way to support
the existing pragmas that are there now. This also recasts it as an annex.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Is this a basis for a slide deck?</span><br><span style=" font-size:10pt;font-family:sans-serif">
David H: My original idea for this was to encourage performance
analysis. It was to allow the optimizer to be turned on at the hot spots.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: We can add that into the reasoning. The pragmas give
that scoping.</span><br><span style=" font-size:10pt;font-family:sans-serif">
*AI* Jim: Draft a slide deck and a proposal based on CFP1331.</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">
Ian: Hard for us to do anything about. It is a fundamental part
of how C is designed.</span><br><span style=" font-size:10pt;font-family:sans-serif">
David H: If you needed this to work, you could enter the number
as a hex constant, pre-rounded how you like.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Ian: A workaround is to have a different pragma around the single
constant and then go back to the normal rounding mode.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Or use the strtod function.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Ian: This is normally execution time.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: We could add a warning note in the documentation (along with
workarounds possibly). Another way would be to not have the pragmas affect
constants. They would take the default rounding mode.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Ian: Does this apply to non-constants as well? Ex. -x? Only if you
want to cast to a different type so not really a problem.</span><br><span style=" font-size:10pt;font-family:sans-serif">
*AI* Jim: Draft a note to warn about CFP1315's rounding of negative
constants issue.</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 (Ex. CFP1307) “fesetexcept() and optional
inexact”</span><br><span style=" font-size:10pt;font-family:sans-serif">
David H: The point of view of the IEEE standard is the second exception
is generated by handling the first one and can be handled differently.
The flags should be viewed as being independent even though they are correlated.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Are we agreed that fesetexcept for overflow/underflow doesn't
allow optional inexact?</span><br><span style=" font-size:10pt;font-family:sans-serif">
Agreed.</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: We want to avoid having WG14 specify what goes into the parenthesis
since that goes beyond what the floating point standard specifies. It could
disallow things the floating point standard intended to allow.</span><br><span style=" font-size:10pt;font-family:sans-serif">
*Keep this item on the agenda for next time.</span><br><br><span style=" font-size:10pt;font-family:sans-serif">
Action items from WG14 London meeting:</span><br><span style=" font-size:10pt;font-family:sans-serif">
C FP: Give 18661 part 4a (not reduction functions) for inclusion
into C2X.</span><br><span style=" font-size:10pt;font-family:sans-serif">
In process. Waiting for a document number.</span><br><span style=" font-size:10pt;font-family:sans-serif">
C FP: Put N2309 into TS 18661-4 and C2X.</span><br><span style=" font-size:10pt;font-family:sans-serif">
rootn: In the document from above.</span><br><span style=" font-size:10pt;font-family:sans-serif">
TS DR13: Move to C2X (C FP action item).</span><br><span style=" font-size:10pt;font-family:sans-serif">
Round result to narrower type: In the part 3 as annex draft.</span><br><span style=" font-size:10pt;font-family:sans-serif">
TS DR16: Move to C2X (C FP action item).</span><br><span style=" font-size:10pt;font-family:sans-serif">
cbrt macro example: Decided on the _Roundwise* were pointers
to functions that are affected by the constant rounding modes. This will
go into C2X.</span><br><span style=" font-size:10pt;font-family:sans-serif">
TS DR20-25: Move to C2X (C FP action item).</span><br><span style=" font-size:10pt;font-family:sans-serif">
DR22 Already in draft, others should be soon.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Tydeman, SD3 1: DR 440: Test macros for FP being 754 types [N 2323]</span><br><span style=" font-size:10pt;font-family:sans-serif">
Result: Want something like N2323 option 1 to be put into
C2X.</span><br><span style=" font-size:10pt;font-family:sans-serif">
The macros concern the format and not anything else. Expected
this is the case.</span><br><br><span style=" font-size:10pt;font-family:sans-serif">
Unnormalized</span><br><span style=" font-size:10pt;font-family:sans-serif">
See Robert Seacord’s SC22WG14.16861, Fred’s SC22WG14.16863, and
Jim’s SC22WG14.16864.</span><br><span style=" font-size:10pt;font-family:sans-serif">
David H: You can have unnormalized extended.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: Aren't these redundant of normals/subnorms?</span><br><span style=" font-size:10pt;font-family:sans-serif">
David H: Yes, different representations. They may
have different arithmetic properties.</span><br><span style=" font-size:10pt;font-family:sans-serif">
David H: Part of the confusion may be terminology, if we
talked about values being normalized or not and avoided talking about subnormalized
it might have helped.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: The floating point model talks about representations
and values which can be confusing.</span><br><span style=" font-size:10pt;font-family:sans-serif">
Jim: This issue may be settled. The ball is in Robert's court.</span><BR>