[cfp-interest 4018] WG14 meeting next week - New CFP potential items and my proposed responses
RAJAN BHAKTA
rbhakta at us.ibm.com
Fri Nov 13 13:48:17 PST 2026
Hello,
In the WG14 meeting starting next week, we will be going over C2Y and C23 issues. Some of the ones that I noticed touch our domain (CFP) are listed here along with my proposed responses. I do intend to bring these up in the next CFP meeting as well, but if I can get early input, I can incorporate it into the meeting responses if we get to these issues.
C2Y issue log, r2 [https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3978.htm]
1100: Should be "What constitutes range errors in non-default rounding modes are implementation-defined."
C23 issue log, r7 [https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3977.htm]
1038: Intent was behavior of use of those types. (float_t, double_t)
Question 1: Intent is that it should be the behaviour in any use of the types, not any program at all.
Question 2: Yes it can be DFP, and if float and double are base 10 types it could work.
Question 3: Yes, but the same restrictions/conditions apply: Implementation defined behaviour since not real floating types.
We can restrict what they types are to real floating types since that seems to be the only practical choice, but that does restrict freedom and is a normative change that does not match the intent.
1046: Seems suggested correction is good. Not sure what changed, but we didn't notice. (powr(y,x) -> powr(x,y))
1062: Intent is to allow it if the implementation wants (efficiency). (SNaNs cause exceptions on assignment?)
Question 1: Implementation defined should still take precedence. This is the most likely case due to efficiency. Most implementations likely do byte-wise or chunk-wise copy on hardware so it would be a burden to require tracking contents and triggering the signal. Matches existing behaviour as well for implementations that I know of.
Question 2: Like question 1. Most likely will be like a trap representation. Signals should only occur only on a read, not assignment.
Question 3: No standard library function should produce a SNaN other than ones that directly modify it (like setting payloads). Uninitialized objects being a SNaN (Ex. malloc'd storage) and then assigned should signal if a read is done just like trap representations.
1074: Interaction between freestanding and feature test macros with conflicting specifications
Question 1: Yes, if __STDC_IEC_60559_COMPLEX__ is not defined, the header is not required. If __STDC_IEC_60559_COMPLEX__ is defined, then that should override the clause 4 since this is a conditionally normative Annex (G) which overrides the main body with its changes.
Question 5: This is a broken implementation as the implementation said no complex types but includes a standard header that includes complex types.
Question 6: Yes, and yes for both parts to the question. It is for the effective setting of access to the floating-point environment, not the textual one. The current wording seems to be clear in any setting of "on" (or "default" when default -> on) precludes it from the entire program, not just the translation unit or section.
Regards,
Rajan Bhakta
CFP
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.oakapple.net/pipermail/cfp-interest/attachments/20261113/804f2ff4/attachment.htm>
More information about the cfp-interest
mailing list