<font size=2 face="sans-serif"> <b>Attendees</b>: Rajan, Jim, Mike,
Fred, Ian, David H.</font><br><br><font size=2 face="sans-serif"><b> New agenda items:</b></font><br><font size=2 face="sans-serif"> Fred's email discussion.</font><br><br><font size=2 face="sans-serif"><b> Last meeting action items:</b></font><br><font size=2 face="sans-serif"> Jim: Activities: Add in
WG14 document numbers to the items that have them. - Done</font><br><font size=2 face="sans-serif"> Rajan: %a precision: If
the footnote is wanted by WG14, correct the typo (differs is several ways
-> differs in several ways) - Done (editorial discretion)</font><br><font size=2 face="sans-serif"> Rajan: %a precision: If
the footnote is wanted by WG14, change "For example" into "For
instance" - Done (editorial discretion)</font><br><font size=2 face="sans-serif"> Jim: Respond to WG14 reflector
message 14812 with the need to have it predictable and fixed - Done (Sent
October 19th)</font><br><font size=2 face="sans-serif"> Jim: Send WG14 N1361 to
the CFP group - Done (October 18th email)</font><br><font size=2 face="sans-serif"> Ian: See if there is an
incompatibility between C and C++ for constants being evaluated to a wider
format (Ex. FLT_EVAL_METHOD affects constants in C++, and wider return
values) - In progress (Hubert: Not defined and left up to C)</font><br><font size=2 face="sans-serif"> Rajan: Willem's paper
point 4 (return value): No consensus but are OK with either way and if
no change, we should note that function return format is not being affected
by FLT_EVAL_METHOD - Done</font><br><font size=2 face="sans-serif"> Fred: Get the latest C
standard paper to the group - Done (Sent email to the password protected
paper, to resend)</font><br><font size=2 face="sans-serif"> All: Discuss via email
Fred's email on 2017/09/21 about Annex F the TS. Potential DR for part
1. - To do today</font><br><font size=2 face="sans-serif"> Jim: Send out alternate
proposal incorporating Willem's points this group agrees on. - Done (N2186)</font><br><br><font size=2 face="sans-serif"><b> New action items:</b></font><br><font size=2 face="sans-serif"> Jim: tgmath_for_narrowing_functions
(DR13, part 3): Need to bring in functions that cover three arguments.</font><br><font size=2 face="sans-serif"> Jim: tgmath_for_narrowing_functions
(DR13, part 3): Rewording for the f32mul example.</font><br><font size=2 face="sans-serif"> Jim: Create a new paper
along the lines of tgmath_for_narrowing_functions proposing a new TC for
CFP DR13.</font><br><font size=2 face="sans-serif"> Jim: Write a DR addressing
WG14 reflector message 14885 using the email sent by Jim on 2017/11/13.</font><br><font size=2 face="sans-serif"> Fred: Look through the
new functions and see what is missing in Annex F.</font><br><font size=2 face="sans-serif"> Fred: Follow up with inconsistencies
in Infinities references in function descriptions in our TS via email.</font><br><font size=2 face="sans-serif"> Fred: Look into 754:2018
4.3.1 (roundTiesToEven) applies to us for string conversion (printf for
example).</font><br><font size=2 face="sans-serif"> Jim: Update the binding
table in parts 1 and 2 to handle the new IEEE-754:2018 functions when published.</font><br><font size=2 face="sans-serif"> David H: Look into the
consistency with our TS and IEEE-754:2018 for 5.3.2, 9.2, 9.2.1, 9.2.2
and 9.4.</font><br><font size=2 face="sans-serif"> Jim: Update activities
list (</font><a href="http://wiki.edg.com/pub/CFP/WebHome/in_flight-20171004.pdf"><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/in_flight-20171004.pdf</font></a><font size=2 face="sans-serif">)
with new status (LaTeX integration) and items (consistency with 754:2018
draft, special cases in Annex F).</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"><b> Next Meetings:</b></font><br><font size=2 face="sans-serif"> January 9th, 2018, 12:00
EDT, 9:00 PST</font><br><font size=2 face="sans-serif"> Same teleconference number.</font><br><br><font size=2 face="sans-serif"><b> Discussion:</b></font><br><font size=2 face="sans-serif"> IEEE 754 revision:</font><br><font size=2 face="sans-serif"> Almost done.</font><br><font size=2 face="sans-serif"> totalOrder issues
- Cost at least a month or two. This is for binary non-basic formats with
canonical and non-canonical representations for the same NaN. The difference
is if getpayload should decode the significand or just report it as a bitfield.</font><br><font size=2 face="sans-serif"> Ian: Implementations
can give their own decode function.</font><br><font size=2 face="sans-serif"> Change for augmented
precision which will cause a change for our proposal (rounding method).</font><br><br><font size=2 face="sans-serif"> C++ liaison:</font><br><font size=2 face="sans-serif"> Nothing new.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> WG14 Meeting:</font><br><font size=2 face="sans-serif"> N2172: Major issue
for rejection was performance.</font><br><font size=2 face="sans-serif"> N2186 will be added
to SD3.</font><br><font size=2 face="sans-serif"> DR12: Good the
way it is. No changes needed.</font><br><font size=2 face="sans-serif"> DR's: Not a defect
according to ISO rules. Our DR's will become Clarification Requests or
something else ("Issues" like C++?). There may be a respository
to track these as well.</font><br><font size=2 face="sans-serif"> Fred: The standard
has been converted to LaTeX and in git. We can start adding part 1 and
2 to the standard (as a branch).</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> Email Issues:</font><br><font size=2 face="sans-serif"> J Myers (SC22WG14.14879)
Floating-point DR#13 and integer arguments to type-generic macros</font><br><font size=2 face="sans-serif"> Need to
fix these.</font><br><font size=2 face="sans-serif"> Jim's 2017/11/13
email (tgmath and narrowing functions) was found when looking at these.</font><br><font size=2 face="sans-serif"> Undefined
behaviour gives most flexibility and easiest fix.</font><br><font size=2 face="sans-serif"> No portable
way to do fadd for _Float32X with long double.</font><br><font size=2 face="sans-serif"> </font><a href=http://wiki.edg.com/pub/CFP/WebHome/tgmath_for_narrowing_functions.pdf><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/tgmath_for_narrowing_functions.pdf</font></a><br><font size=2 face="sans-serif"> *Jim:
tgmath_for_narrowing_functions: Need to bring in functions that cover three
arguments.</font><br><font size=2 face="sans-serif"> *Jim:
tgmath_for_narrowing_functions: Rewording for the f32mul example.</font><br><font size=2 face="sans-serif">
</font><br><font size=2 face="sans-serif"> J Myers (SC22WG14.14885)
Comparison macros and usual arithmetic conversion</font><br><font size=2 face="sans-serif"> Jim's email
on 2017/11/13 looks good.</font><br><font size=2 face="sans-serif"> We never
meant for comparisons for things that are not comparable.</font><br><font size=2 face="sans-serif"> *Jim: Write
a DR addressing WG14 reflector message 14885.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> Freds email re
Annex F (2017/9/21): </font><br><font size=2 face="sans-serif"> Jim: I don't
think we itemize anything for sqrt</font><br><font size=2 face="sans-serif"> Fred: I
think we do in the existing C99!</font><br><font size=2 face="sans-serif"> Jim: I think
it says sqrt is fully specified in 60559.</font><br><font size=2 face="sans-serif"> Jim: We
need to review Annex F for all the new functions. Nothing substantive since
we have already made the specification by reference.</font><br><font size=2 face="sans-serif"> We
figured C standard readers didn't want to cross reference 754 all the time.</font><br><font size=2 face="sans-serif"> Note
that we didn't do that for totalOrder (we referred to 754).</font><br><font size=2 face="sans-serif"> *Fred: Look
through the new functions and see what is missing in Annex F.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> Fred: Should the
main body of the standard call out exception cases to Inf?</font><br><font size=2 face="sans-serif"> Jim: Infinity
is not part of the basic model in the C standard.</font><br><font size=2 face="sans-serif"> Fred: fmul
for example lists domain error for INF and 0. fadd and fsub do not say
it for infinities of different signs. I suggest we add words to say it
should have a domain error. Jim's response was we shouldn't do that since
we don't normally do it in the C standard (with a few exceptions, including
where it is essential to the function) and the TS should be consistent
with C.</font><br><font size=2 face="sans-serif"> Fred: There
are inconsistencies that should be fixed in the TS. Will follow up in email.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> Binding for IEEE 754-2018:</font><br><font size=2 face="sans-serif"> Augmented: Mostly
stable.</font><br><font size=2 face="sans-serif"> Min/Max: Stable.</font><br><font size=2 face="sans-serif"> Payload: Waiting
for it to be stable in 754.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> Email on 2017/11/14
from Jim (Changes in 754):</font><br><font size=2 face="sans-serif"> 4.3.1 (roundTiesToEven)
applies to us for string conversion (printf for example).</font><br><font size=2 face="sans-serif"> *Fred
to look into this.</font><br><font size=2 face="sans-serif"> 5.3.1 (preferred
exp): Already have it.</font><br><font size=2 face="sans-serif"> 5.3.1 {min,max}Num{Mag}:
Already covered with our new proposal. Need to update the binding table
in parts 1 and 2.</font><br><font size=2 face="sans-serif"> *Jim:
Update the binding table in parts 1 and 2 to handle the new IEEE 754 functions
when published.</font><br><font size=2 face="sans-serif"> 5.3.2 (quantum
operation): Need to check for consistency</font><br><font size=2 face="sans-serif"> *David
H. to look into this.</font><br><font size=2 face="sans-serif"> 5.7.1 (predicate
operation): Not in C. We do have references to 60559:2011. These need to
change to 2018.</font><br><font size=2 face="sans-serif"> 60559
last time had a 3 year delay from the IEEE-754 standard.</font><br><font size=2 face="sans-serif"> We
have macros that are defined with the value of a date that refers to the
TS timing, not 60559.</font><br><font size=2 face="sans-serif"> Just
need to track it.</font><br><font size=2 face="sans-serif"> 9.2 (new
aSinPi, aCosPi): Present in part 1. Added to IEEE based on our spec. Need
consistency check.</font><br><font size=2 face="sans-serif"> *David
H. to look into this.</font><br><font size=2 face="sans-serif"> 9.2.1 (new
cases for pow): Present in part 1. Added to IEEE based on our spec. Need
consistency check.</font><br><font size=2 face="sans-serif"> *David
H. to look into this.</font><br><font size=2 face="sans-serif"> 9.2.2 (preferred
exponents): Consistency check.</font><br><font size=2 face="sans-serif"> *David
H. to look into this.</font><br><font size=2 face="sans-serif"> 9.4 (inexact
exception): Consistency check.</font><br><font size=2 face="sans-serif"> *David
H. to look into this.</font><br><font size=2 face="sans-serif"> 9.5 (new
augmented functions): Covered already.</font><br><font size=2 face="sans-serif"> 9.6 (new
min/max functions): Covered already.</font><br><font size=2 face="sans-serif"> 9.7 (new
get/set/setsignaling payload operations): Covered.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> Activities (</font><a href="http://wiki.edg.com/pub/CFP/WebHome/in_flight-20171004.pdf"><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/in_flight-20171004.pdf</font></a><font size=2 face="sans-serif">):</font><br><font size=2 face="sans-serif"> 1, 2) Look at the
LaTeX version of the document and into integrating the DR's.</font><br><font size=2 face="sans-serif"> 3-5c, TONEARESTFROMZERO)
Update for next WG14 meeting.</font><br><font size=2 face="sans-serif"> cbrt example) Need
to invite Clark to the next CFP meeting.</font><br><font size=2 face="sans-serif"> Updating to 754:2018,
augmented, min/max, payload) Wait for publish before we present this.</font><br><font size=2 face="sans-serif"> Willem's issues)
Wait for Willem's reponse.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> New item: Checking
consistency with 754:2018 draft.</font><br><font size=2 face="sans-serif"> New item: Filling
in special cases in Annex F.</font><br><font size=2 face="sans-serif"> Possible new item:
Fred's consistency check for Infinities specification.</font><br><font size=2 face="sans-serif"> *Jim: Update activities
list with new status.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> We could update
part 1, 2, etc. with the closed DR's and use them as the base document
for WG14 to look at when considering inclusion into C2X.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> Other:</font><br><font size=2 face="sans-serif"> None.</font><br><BR>