[cfp-interest 4025] C FP Paper results in the 2026/11/16 WG14 meeting

RAJAN BHAKTA rbhakta at us.ibm.com
Tue Nov 17 10:39:42 PST 2026


Hello,

Here are the raw notes and action items I have for our C FP papers. Please feel free to add any additions if Joshua (or others) have any.

I will follow up with another email for the results of the C2Y and C23 issues (if applicable) which is currently planned to be discussed on Thursday (but may move up earlier).

Notations:
  ^ Indicates action items or votes. Search for this if you want just the core points we need to know or deal with.
---

N3877: Sign of 0 returned by fromfp
    Cranmer: LLVM and libc return -0.
    Ballman: Michael Jones from LLVM libc said that this seems fine but not sure about the -0 to +0 change.

    ^Decision poll: Put N3877 (sign of 0 from fromfp) into C2Y?
      4+8/0+0/0+4. 12/0/4. Goes into C2Y.

N3962: Clarification of requirements in Annex H
    ^Decision poll: Put N3962 (Annex H fixes) into C2Y?
      3+9/0+0/0+2. 12/0/2. Goes into C2Y.

N3943: Annex F: Special cases rework
    Thiago: Using math symbol for infinite. Should we use INF instead of NaN?
    Banham: The "y a quiet NaN" should be worded better. Add "is".
    ^Joseph: [SC22WG14.38450] comments for the paper.
      1. Additional statements are added for atan2 and atan2pi, "atan2 (−y, x) and -atan2 (y, x) are equivalent" and "atan2pi (−y, x) and -atan2pi (y, x) are equivalent", described as "[Not a new requirement - see F.10.1#3]".  But such equivalence for an odd function is only true in certain rounding modes, not for rounding upward or downward.
      2. ilogb is 7.12.7.8 not 7.12.6.8 (the edits change a correct subclause number to an incorrect one).

    ^Opinion poll: Want something like N3943 (Annex F special cases rework) with Josephs comments addressed in C2Y?
      2+14/0+0/1+3. 16/0/4. Clear direction.

N3942: Annex F: Introduction changes
    ^Joseph:: SC22WG14.38428 has my comments
      1. I don't think the new table headings, describing them as "Mandated" / "Recommended" operations, are accurate - aren't the maximum / minimum operations actually recommended ones (albeit ones deliberately listed in the first table and required to give exact results)?  (Likewise the changes to text in F.3 about what each table contains.)
      2. There's a reference to DEC_RADIX, but no such macro exists.
      3. The second reference to convertToIntegerTiesToEven should be convertToIntegerExactTiesToEven.
      4. "(of a real floating type)" in reference to FLT_RADIX isn't correct since the decimal floating types are also real floating types; probably "(of a standard floating type)" is meant.
      5. I'm not convinced by the changes in F.10.1 to refer to table F.4 instead of table F.1 - I think all those references were correctly about the main operation binding table, not about the subsequent one (F.4 after these changes) for operations that are not required to be correctly rounded, and so should not be changed.

    ^Opinion poll: Want something like N3942 (Annex F introduction rework) in C2Y?
      17/0/2. Clear direction.

    Joseph: For printf SNAN, the ambiguity is for the convertFormat vs copy operation as well.
    Cranmer: The IEEE functions convert to character don't give enough information either.
    Ballman: I don't want SNaN to be handled differently from varargs.
    Cranmer: vararg has float converted to double due to default argument promotions.


N3947: nexttoward and nextafter
    ^CFP: Look at WG14 message 38263 (https://www.open-std.org/jtc1/sc22/wg14/38263).
    Joseph: Message 38263.
    Joseph: For a macro, what happens? And for evaluation formats, it talks about casts but not clear what happens with extra range and precision.
    Ballman: Will we break users by doing this?
    Rajan: Possibly. But this is fixing a wrong result in the standard.
    Joseph: Not sure this is forward progress since it loses the removal of excess range and precision is a problem.


 N3948: quantum exponent of fromfp family
    Cranmer: Only 2 implementations are glibc and llvm libc. Don't know if they implement this.

    ^Decision poll:  Would WG14 like to adopt N3948 into the C2Y working draft?
      2+4/0+0/1+7. 6/0/8. Consensus to adopt.

Regards,

Rajan Bhakta
CFP

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.oakapple.net/pipermail/cfp-interest/attachments/20261117/31a18c23/attachment-0001.htm>


More information about the cfp-interest mailing list