<font size=2 face="sans-serif"><b>Attendees</b>: Rajan, Jim, Fred, Mike,
David, Ian, Blaine</font><br><br><font size=2 face="sans-serif"><b>New agenda items</b>:</font><br><font size=2 face="sans-serif"> WG14 mailing paper N2016
on half float.</font><br><br><font size=2 face="sans-serif"><b>Last meeting action items</b>:</font><br><font size=2 face="sans-serif"> Ian: Talk to Lawrence
Crowl regarding proposing this IEEE-754: 2008 binding to C++ as well. -
In process.</font><br><font size=2 face="sans-serif"> Ian: Update and check
the items listed and flagged under Feature_List_Part_1. - Not done.</font><br><font size=2 face="sans-serif"> All: Focused Review of
part 5 once the updated draft comes out. - Done.</font><br><br><font size=2 face="sans-serif"> Jim: Part 5: p12: Line
14: Change to "supports reproducible results for decimal floating
types." or something similar. - Done.</font><br><font size=2 face="sans-serif"> Jim: Part 5: Page 12,
line 14; Page 13, line 3: Check the wording here to see if the standard
does this (enumerate values and then later says it can have other values).
- Done (no change).</font><br><font size=2 face="sans-serif"> Jim: Part 5: Page 5 line
9: occurances -> occurrence - Done.</font><br><font size=2 face="sans-serif"> Jim: Part 5: Page 10:
Line 25: semantic type*s* -> semantic type. May occur in other places
in the document (Ex. Page 9, Line 22; Page 19, Line 23) - Done.</font><br><font size=2 face="sans-serif"> Jim: Part 1: Page 51:
Line 3: Add a footnote to the 'l suffix' stating there are no functions
with the 'f' suffix. - Done.</font><br><font size=2 face="sans-serif"> Rajan: Send the DR template
to Jim for parts 1-4 issues to get them ready in time for the WG14 meeting.
- Done.</font><br><font size=2 face="sans-serif"> Jim: Post updated versions
of TS parts on the wiki. - Not done.</font><br><font size=2 face="sans-serif"> David: Note about our
group work from the IEEE sent to Rajan/Fred - Not done.</font><br><br><font size=2 face="sans-serif"><b>New action items</b>:</font><br><font size=2 face="sans-serif"> Jim: Possible Defects:
Part 2: Change set 2 (feature macros and tgmath.h): Create a new DR paper
for requiring the macro to be defined before tgmath.h inclusion.</font><br><font size=2 face="sans-serif"> Jim: Possible Defects:
Part 1: Change set 1 (typos): Change to make it fetestexceptflag as the
typo fix.</font><br><font size=2 face="sans-serif"> Rajan: Talk to David Keaton
to get N2016 discussed when Mike is present (Monday).</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"><b>Next Meeting</b>:</font><br><font size=2 face="sans-serif"> April 26th, 2016, 12:00
EST, 9:00 PDT</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"> Making gradual
progress.</font><br><font size=2 face="sans-serif"> Knock off about
one item per meeting.</font><br><font size=2 face="sans-serif"> Haven't needed
a vote yet.</font><br><font size=2 face="sans-serif"> Agenda getting
shorter as well.</font><br><font size=2 face="sans-serif"> Discussion about
future enhancements beyond this revision. Ex. add/sub instructions with
rounding away from zero. Helps double double and reproducibility.</font><br><font size=2 face="sans-serif"> Last time
this discussion focused on the hardware, this time it will be software.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> Arith23:</font><br><font size=2 face="sans-serif"> No change to plan
known.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> Wider WG14:</font><br><font size=2 face="sans-serif"> Item for LaTeX
on the agenda in the next WG14 meeting.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> Part 5: Various emails,
documents submitted for the mailing (slides, TS):</font><br><font size=2 face="sans-serif"> Scheduled for WG14
on Monday (first day). Mike should be able to attend.</font><br><font size=2 face="sans-serif"> Hope to have it
ready for ballot after this meeting after the final changes.</font><br><font size=2 face="sans-serif"> Chance to have
the entire process done by 2017.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> Parts 1-4:</font><br><font size=2 face="sans-serif"> DRs: </font><a href="http://wiki.edg.com/pub/CFP/WebHome/DRs-20160310.pdf"><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/DRs-20160310.pdf</font></a><br><font size=2 face="sans-serif"> Changes
to part 1:</font><br><font size=2 face="sans-serif"> Change
set 1 (typos): OK. *Jim: With change to make it 'fe'testexceptflag as the
typo fix.</font><br><font size=2 face="sans-serif"> Change
set 2 (narrower type):</font><br><font size=2 face="sans-serif">
Rajan/Fred: Clearer if we delete everything from "Page 40: ..."
to "In 7.12.13a#1, ".</font><br><font size=2 face="sans-serif">
Jim: The position is there to put the footnote on page 40 to indicate
the end of the section that is affected by the change.</font><br><font size=2 face="sans-serif">
This is for a change to the TS, not to the C standard. Deleting
the text would make it inconsistent with other TS specified changes to
C.</font><br><font size=2 face="sans-serif">
Perhaps add a paragraph in the summary "the suggested TC below
adds the statement with a footnote to show what it says"?</font><br><font size=2 face="sans-serif">
Leave it as is for now.</font><br><font size=2 face="sans-serif"> Change
set 3 (nonexistent case): OK.</font><br><font size=2 face="sans-serif"> Changes
to part 2:</font><br><font size=2 face="sans-serif"> Change
set 1 (typos): OK.</font><br><font size=2 face="sans-serif"> Change
set 2 (feature macros and tgmath.h): Blaine: Is this implementable? Jim:
We did it at HP by declaring the functions (not reincluding math.h) under
a no math.h inclusion macro check.</font><br><font size=2 face="sans-serif">
It can be done by simple means but any other changes in math.h need to
be handled if a reinclusion needs to be done.</font><br><font size=2 face="sans-serif">
Fred: Make the 'want' macros have to be declared before any std headers
are included.</font><br><font size=2 face="sans-serif">
This would make it undefined behaviour otherwise.</font><br><font size=2 face="sans-serif">
Other options: Force reinclusion of math.h.</font><br><font size=2 face="sans-serif">
Would result in possible changes due to other macros declaring other
functions (perhaps incompatibly).</font><br><font size=2 face="sans-serif">
K.3.1.1p4 seems to imply that we already have this under the existing
C standard. Jim: The requirement of a diagnostic addresses my usability
concerns.</font><br><font size=2 face="sans-serif">
*Jim: Create a new DR for this approach.</font><br><font size=2 face="sans-serif"> Changes
to part 3:</font><br><font size=2 face="sans-serif"> Change
set 1 (typos): OK.</font><br><font size=2 face="sans-serif"> Change
set 2 (Error in function name): OK.</font><br><font size=2 face="sans-serif"> Change
set 3 (Feature macro interactions): If you don't have the names exposed
due to not defining the want macro, do you still get the extended function
declarations? Yes. Current specification says that.</font><br><font size=2 face="sans-serif">
You can have some functions without type generic macros for them (nextup
for example).</font><br><font size=2 face="sans-serif">
Rajan: We could just say it is valid. No change needed to the TS. Use the
DR process to answer the question.</font><br><font size=2 face="sans-serif">
Blaine: Classic case of DR to answer a question. Leave it as is (no change
to the TS).</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> Half float (N2016):</font><br><font size=2 face="sans-serif"> Mike: No defined
width and no defined arithmetic.</font><br><font size=2 face="sans-serif"> Makes it
not portable/standardized.</font><br><font size=2 face="sans-serif"> They are
also using a useful name slot (syntax).</font><br><font size=2 face="sans-serif"> Jim: Makes it useless
for portability and may end up hurting it (in the paper they have different
names already).</font><br><font size=2 face="sans-serif"> Mike: You can just
do '#define ShortFloat <whatever>' and it would be just as useful.</font><br><font size=2 face="sans-serif"> _Float16x type:
Not in 754 or our TS. The issue is the differences that already exist for
types like this.</font><br><font size=2 face="sans-serif"> *Rajan: Talk to
David Keaton to get this paper discussed when Mike is present (Monday).</font><br><font size=2 face="sans-serif"> The same name should
not mean something completely different.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif"> What should be proposed
for the C standard:</font><br><font size=2 face="sans-serif"> Discuss next meeting.</font><br><font size=2 face="sans-serif"> </font><br><font size=2 face="sans-serif">Regards,<br><br>Rajan Bhakta<br>z/OS XL C/C++ Compiler Technical Architect<br>ISO C Standards Representative for Canada<br>C Compiler Development<br>Contact: rbhakta@us.ibm.com, Rajan Bhakta/Houston/IBM</font><BR>