<font size=2 face="sans-serif"> <b>Attendees</b>: Rajan, Jim, Fred,
Ian, David H., Mike, David C.</font><br><br><font size=2 face="sans-serif"><b> New agenda items:</b></font><br><font size=2 face="sans-serif"> None.</font><br><br><font size=2 face="sans-serif"><b> Last meeting action items:</b></font><br><font size=2 face="sans-serif"> Rajan: Submit DRS2:DDR9
example as a paper for a supplement to the STC in the DR and change all
the %A to %a (ensuring it conforms to the specification for %a). - Done
(N2126)</font><br><font size=2 face="sans-serif"> Jim: Create a DR against
part 2 to specify the capitalization effects of %a. - Done (N2125)</font><br><font size=2 face="sans-serif"> Jim: DRs2:DDR2: DECIMAL_DIG:
Have DECIMAL_DIG to be the largest supported floating type as a new replacement
Suggested TC for DRs2:DDR2. - Not done due to further discussion. Remove
from list.</font><br><font size=2 face="sans-serif"> Jim: Add in the encoding
*_DIG macros (as per </font><a href="http://wiki.edg.com/pub/CFP/WebHome/characteristics_for_non-arith_formats.pdf"><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/characteristics_for_non-arith_formats.pdf</font></a><font size=2 face="sans-serif">)
and obsolescing DECIMAL_DIG as a proposal to WG14 as a new enhancement.
- Not done due to further discussion. Remove from list.</font><br><font size=2 face="sans-serif"> Jim: Include Type-generic
macros for functions that round result to narrower type as part of the
third set of DR's. - Done (N2125).</font><br><font size=2 face="sans-serif"> Fred: Propose adding in
#pragma STDC FENV_ROUND DEFAULT as a means to set the static rounding mode
to the default rounding mode. - Done (N2128) via a different method.</font><br><br><font size=2 face="sans-serif"><b> New action items:</b></font><br><font size=2 face="sans-serif"> Rajan: Bring up "Understanding"
points 4 and 5 when discussing DR501 (from Jim's email on 2017/03/17).</font><br><font size=2 face="sans-serif"> David H: Ask about the
IEEE dependencies (rounding mode, infinities) for the augmented functions
and how they could be used for non-IEEE formats.</font><br><font size=2 face="sans-serif"> Jim: Ask David Keaton
what we should be doing to close off the group or extend it (IEEE-754:2018
binding for example).</font><br><br><font size=2 face="sans-serif"><b> Next Meeting:</b></font><br><font size=2 face="sans-serif"> Tuesday April 25th, 2017,
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"> Near the end.</font><br><font size=2 face="sans-serif"> Couple of major
items without text: Max/min, augmented.</font><br><font size=2 face="sans-serif"> What to
do the old min/max? Remove? Deprecate? Currently deprecated is not a concept.
Instead we say you can do x and y, but you should do y.</font><br><font size=2 face="sans-serif"> Currently everything
added is a recommendation. Next revision may consider making changes that
are required and may cause changes.</font><br><br><font size=2 face="sans-serif"> C++ liaison:</font><br><font size=2 face="sans-serif"> No update.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> Proposals for the C standard
(C2X):</font><br><font size=2 face="sans-serif"> Links in email
sent by Jim today.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> DRs:</font><br><font size=2 face="sans-serif"> N2127 (</font><a href=http://wiki.edg.com/pub/CFP/WebHome/n2127.pdf><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/n2127.pdf</font></a><font size=2 face="sans-serif">):</font><br><font size=2 face="sans-serif"> Proposed
change to Part 3 for DR 501.</font><br><font size=2 face="sans-serif"> This paper
changes part 2 in a simpler way which means part 3 does not need to change
anymore.</font><br><font size=2 face="sans-serif"> N2126 (</font><a href=http://wiki.edg.com/pub/CFP/WebHome/N2126__Example_of_the_effect_of_the_change_for_CFP_DR11.htm><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/N2126__Example_of_the_effect_of_the_change_for_CFP_DR11.htm</font></a><font size=2 face="sans-serif">):</font><br><font size=2 face="sans-serif"> No capital
A to avoid the %A specification issue (which is handled via another paper).</font><br><font size=2 face="sans-serif"> Discuss DECIMAL_DIG
issues (Jim's 3/17/17 email):</font><br><font size=2 face="sans-serif"> "Understanding":</font><br><font size=2 face="sans-serif"> Point
2:</font><br><font size=2 face="sans-serif">
Ian: Regarding extension floating-point types vs extended integer types:
We should see about changing the C standard to support this.</font><br><font size=2 face="sans-serif">
Jim: This is essentially what we're doing in part 3.</font><br><font size=2 face="sans-serif"> Point
3:</font><br><font size=2 face="sans-serif">
Common extensions are not necessarily conforming.</font><br><font size=2 face="sans-serif"> Point
4:</font><br><font size=2 face="sans-serif">
Since it doesn't say long double, this follows.</font><br><font size=2 face="sans-serif"> "Alternatives":</font><br><font size=2 face="sans-serif"> Point
2: Seems to be more acceptable to be a C2X proposal since WG14 did not
seem to like making changes to C due to a TS.</font><br><font size=2 face="sans-serif"> Point
4: Will have to be a proposal for a new version of part 3 (or part of C
if the Part 3 proposal for C2X gets in).</font><br><font size=2 face="sans-serif"> Alternative
2 seems to be the consensus.</font><br><font size=2 face="sans-serif"> Can
bring up "Understanding" points 4 and 5 when discussing DR501.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> Binding for IEEE 754-2018
(Jim's email on 2017/03/20):</font><br><font size=2 face="sans-serif"> Augmented operations:
Return two results, head and tail.</font><br><font size=2 face="sans-serif"> WG14 said
a struct is better to return two results.</font><br><font size=2 face="sans-serif"> Non-IEEE
format needs to be looked at. Rounding mode, infinities for example do
not always exist.</font><br><font size=2 face="sans-serif"> David H:
Perhaps say the two parts need to add up to the correct result to leave
slack in terms of rounding.</font><br><font size=2 face="sans-serif"> Jim: There
are algorithms for reproducible summations (the purpose of these functions).
Those algorithms likely need this rounding property to work correctly.
It does not need to be a rounding mode, just the result has to follow that
property.</font><br><font size=2 face="sans-serif"> David
H: The property was an issue of efficiency. May not be possible for non-IEEE
due to implicit dependencies.</font><br><font size=2 face="sans-serif"> Ian: For
AIX double-double (vs Linux double-double), having the high part being
close to infinity may have issues as rounding away from zero may result
in an infinity.</font><br><font size=2 face="sans-serif"> Ian: No
rounding mode that works in general for IEEE.</font><br><font size=2 face="sans-serif"> David
H: It does for Decimal.</font><br><font size=2 face="sans-serif">
It was not intended that they add another mode, just that the semantics
have this.</font><br><font size=2 face="sans-serif"> Ian: Most
implementations do not have the rounding mode needed.</font><br><font size=2 face="sans-serif"> David H:
Expected that we can implement this in hardware.</font><br><font size=2 face="sans-serif"> Ian:
If we are expecting hardware to add this rounding for these operations,
would it work for a general rounding mode?</font><br><font size=2 face="sans-serif">
David H: No, since most hardware only has 2 bits for rounding mode and
adding this would result in another bit.</font><br><font size=2 face="sans-serif"> Non-IEEE
implementations: double-double to get quad-quad, short/half (hard to imagine),
IBM Hex format (only has round to zero), packed decimal?</font><br><font size=2 face="sans-serif"> Jim: Annex
F allows double-double for 'long double'. </font><br><font size=2 face="sans-serif"> *David H:
Ask about the IEEE dependencies (rounding mode, infinities) for the augmented
functions and how they could be used for non-IEEE formats.</font><br><font size=2 face="sans-serif"> Min/Max:</font><br><font size=2 face="sans-serif"> NaN preference
or number preference.</font><br><font size=2 face="sans-serif"> Can do fminISO,
fminIEC, fminSTD or something like that.</font><br><font size=2 face="sans-serif"> Mike: fminimum
can be used. No reason to abbreviate.</font><br><font size=2 face="sans-serif"> Fred: In
Annex F we don't say anything about zeros or SNaNs.</font><br><font size=2 face="sans-serif"> Jim:
In the TS we do say SNaNs always signal. The signed zero will likely break
a lot of implementations of the existing fmin (which is more like minimumNumber).</font><br><font size=2 face="sans-serif"> Rajan: There
are long names already for the atomic functions. Can just do fminimum_magnitude_number.</font><br><font size=2 face="sans-serif"> We can discuss
this next meeting after thinking about it.</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"> Marius (pre-meeting
question): When will things be finalized?</font><br><font size=2 face="sans-serif"> Fred: After
C2X?</font><br><font size=2 face="sans-serif"> Jim: We
need to stay with it until it is in the standard. This will take a while.</font><br><font size=2 face="sans-serif"> If
parts go into the standard but not all of them, we need to revise the TS
parts that didn't go in (Ex. rebase on C2X).</font><br><font size=2 face="sans-serif"> Rajan: Current
WG14 mandate is for IEEE-754:2008 binding. The 2018 binding may be something
we add on or a new group created.</font><br><font size=2 face="sans-serif"> *Jim: Ask
David Keaton what we should be doing to close off the group or extend it
(IEEE-754:2018 binding for example).</font><br><font size=2 face="sans-serif"> Jim: WG14
will likely be happy to have us help integrate any parts into C2X.</font><BR>