<font size=2 face="sans-serif"> <b>Attendees</b>: Rajan, Jim, Fred,
Ian, Mike, Marius, David H.</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"> Jim: Check one of the
files from the EDG backup for testing the off site backup. - Not done.</font><br><font size=2 face="sans-serif"> Jim: Update the proposal
for Part 2 to make it more similar to Part 1's proposal. - Done.</font><br><font size=2 face="sans-serif"> Jim: For all proposals:
Change to "This proposal incorporates" as the starting. - Done.</font><br><font size=2 face="sans-serif"> Rajan: Proposal 1: Update
the spreadsheet of part 1 features based on Marius' note and send it out
to the group for final review. - Done.</font><br><font size=2 face="sans-serif"> Rajan: Proposal 1: Change
the prior art text that has "ex." to "Example:" since
Ex. could mean excluding. - Done.</font><br><font size=2 face="sans-serif"> Rajan: Proposal 2: Add
in prior art based off the spreadsheet of features. - Done.</font><br><font size=2 face="sans-serif"> Jim: Proposal 4b: Mention
underflow as well (alongside the existing overflow). - Done.</font><br><font size=2 face="sans-serif"> Jim: Proposal 5a: Look
at leaving out the types in the second paragraph. - Done.</font><br><font size=2 face="sans-serif"> Jim: Proposal 5d: Title:
alternate expression handling -> alternate exception handling - Done.</font><br><font size=2 face="sans-serif"> Jim: Proposal 5d: Say
"portable handling of exceptional cases". - Done.</font><br><font size=2 face="sans-serif"> Jim: Proposal 5d: Simplify
the abstract by removing the detail after "Some actions control".
- Done.</font><br><font size=2 face="sans-serif"> Jim: Proposal 5d: Say
"The pragma allows the program to deal with exceptional cases without
having to consider implementation details." - Done.</font><br><font size=2 face="sans-serif"> Jim: DDR7: Integrate the
changes proposed for the usual arithmetic conversions into a combined document
to make it easier to read/understand. - Done.</font><br><font size=2 face="sans-serif"> Jim: DDR?: Create a new
DDR for the typo that Joseph just raised in reflector message 14358. -
Done. DR#8.</font><br><font size=2 face="sans-serif"> Jim: Consult with Mike
to discuss the preferred quantum exponent for hypot (in the TS), rsqrt,
pow* (in the TS), etc. - Done.</font><br><br><font size=2 face="sans-serif"> <b>New action items</b>:</font><br><font size=2 face="sans-serif"> General: Need to look
through our docs to see what is in C but not in IEEE 754.</font><br><font size=2 face="sans-serif"> All: Look through WG14
proposals and let Rajan and Jim know if there is anything that we need
to bring up.</font><br><font size=2 face="sans-serif"> Jim: DDR9: Update type
style.</font><br><font size=2 face="sans-serif"> Jim: DDR9: Update examples
as per Fred's note.</font><br><br><font size=2 face="sans-serif"> <b>Next Meeting</b>:</font><br><font size=2 face="sans-serif"> October 25th, 2016, 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"> Next WG14 meeting (Pittsburgh,
2016/10/17) had a September 19th mailing deadline.</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"> Converging.</font><br><font size=2 face="sans-serif"> Some drafting for
comparisons left.</font><br><font size=2 face="sans-serif"> augmentedSum, augmentedProduct
names.</font><br><font size=2 face="sans-serif"> Incorporated suggestions
for preferred quantum exponents for transcendentals.</font><br><font size=2 face="sans-serif"> Note that
we had decided to do the same if 754 did it (as a DR to Part 4). Can wait
until settled in 754.</font><br><font size=2 face="sans-serif"> Fred: Rules
do not allow adding new features through DR's.</font><br><font size=2 face="sans-serif"> We
can talk to David Keaton on how to do this after.</font><br><br><font size=2 face="sans-serif"> C++ liaison:</font><br><font size=2 face="sans-serif"> No updates.</font><br><br><font size=2 face="sans-serif"> twoSum, twoProduct (now
augmentedSum, augmentedProduct) for TS 18661 update:</font><br><font size=2 face="sans-serif"> The C committee
responded to the C interface that we should return a struct with two members.</font><br><font size=2 face="sans-serif"> Wait to add until
settled as discussed above.</font><br><font size=2 face="sans-serif"> Jim: acospi/asinpi
missing, agreed that they are missing, but declined to add them.</font><br><font size=2 face="sans-serif"> All those
functions are optional.</font><br><font size=2 face="sans-serif"> Should 754
add them?</font><br><font size=2 face="sans-serif"> David H:
I would support adding them. Obvious oversight. Will add it to the IEEE
754 agenda.</font><br><font size=2 face="sans-serif"> We
already have it in our TS.</font><br><font size=2 face="sans-serif"> Ian: Are
there other functions that should be added? Example: Is there an atanpi
function?</font><br><font size=2 face="sans-serif"> Jim: tanpi is not
there since there are issues (sign of inf depends on direction of approach).</font><br><font size=2 face="sans-serif"> Mike: Anything
else in C that is not in 754?</font><br><font size=2 face="sans-serif"> *General:
Need to look through our docs to see what is in C but not in IEEE 754.</font><br><br><font size=2 face="sans-serif"> What should be proposed
for the C standard:</font><br><font size=2 face="sans-serif"> Rajan will present
the proposals.</font><br><font size=2 face="sans-serif"> N2078, N2079 are
the WG docs.</font><br><font size=2 face="sans-serif"> *All: Look through
WG14 proposals and let Rajan and Jim know if there is anything that we
need to bring up.</font><br><br><font size=2 face="sans-serif"> DRs review (</font><a href="http://wiki.edg.com/pub/CFP/WebHome/DRs2-20160910.pdf"><font size=2 color=blue face="sans-serif">http://wiki.edg.com/pub/CFP/WebHome/DRs2-20160910.pdf</font></a><font size=2 face="sans-serif">):</font><br><font size=2 face="sans-serif"> DDR8: Typo that
amounts to an interface change hence not editorial.</font><br><br><font size=2 face="sans-serif"> DDR9: Fred's comment
regarding italics will need to be made.</font><br><font size=2 face="sans-serif"> Jim: The
type style is not consistent throughout the document in general. Planning
on doing it like the TS.</font><br><font size=2 face="sans-serif"> Fred: Example
needs to be updated and that needs to be added in to this DDR.</font><br><font size=2 face="sans-serif"> Jim: The
TR says there is a rounding on the type, and that is what the TS is based
on.</font><br><font size=2 face="sans-serif"> This
means that existing implementations would be incorrect.</font><br><br><font size=2 face="sans-serif"> Other:</font><br><font size=2 face="sans-serif"> None.</font><br><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><BR>