[1003.1(2013)/Issue7+TC1 0000713]: in remquo quo should be unspecified when the result is NaN
The following issue has a resolution that has been APPLIED. == https://austingroupbugs.net/view.php?id=713 == Reported By:nsz Assigned To: == Project:1003.1(2013)/Issue7+TC1 Issue ID: 713 Category: System Interfaces Type: Omission Severity: Editorial Priority: normal Status: Applied Name: Szabolcs Nagy Organization: musl User Reference: Section:remquo Page Number: Line Number: Interp Status: --- Final Accepted Text:See https://austingroupbugs.net/view.php?id=713#c5527. Resolution: Accepted As Marked Fixed in Version: == Date Submitted: 2013-06-18 00:00 UTC Last Modified: 2021-12-13 14:58 UTC == Summary:in remquo quo should be unspecified when the result is NaN == Issue History Date ModifiedUsername FieldChange == 2013-06-18 00:00 nszNew Issue 2013-06-18 00:00 nszName => Szabolcs Nagy 2013-06-18 00:00 nszOrganization => musl 2013-06-18 00:00 nszSection => remquo 2013-06-20 15:54 nick Tag Attached: c99 2021-04-14 15:01 nick Note Added: 0005312 2021-04-14 15:23 kreNote Added: 0005313 2021-04-14 15:28 kreNote Added: 0005314 2021-04-15 09:08 geoffclare Note Added: 0005317 2021-04-15 19:58 kreNote Added: 0005319 2021-04-15 19:58 kreNote Deleted: 0005313 2021-04-15 19:59 kreNote Edited: 0005319 2021-06-16 00:40 nick Note Added: 0005379 2021-06-16 08:17 Vincent LefevreNote Added: 0005380 2021-06-16 18:25 shware_systems Note Added: 0005381 2021-06-16 18:27 Don Cragun Note Added: 0005382 2021-06-16 18:28 Don Cragun Note Edited: 0005382 2021-06-16 18:30 shware_systems Note Edited: 0005381 2021-06-16 22:19 Vincent LefevreNote Added: 0005383 2021-06-17 12:30 kreNote Added: 0005384 2021-11-18 13:30 nick Note Added: 0005526 2021-11-18 16:17 Don Cragun Note Added: 0005527 2021-11-18 16:20 Don Cragun Note Edited: 0005527 2021-11-18 16:21 Don Cragun Interp Status => --- 2021-11-18 16:21 Don Cragun Final Accepted Text => See https://austingroupbugs.net/view.php?id=713#c5527. 2021-11-18 16:21 Don Cragun Status New => Resolved 2021-11-18 16:21 Don Cragun Resolution Open => Accepted As Marked 2021-11-18 16:22 Don Cragun Tag Attached: tc3-2008 2021-11-18 16:22 Don Cragun Note Edited: 0005527 2021-12-13 14:58 geoffclare Status Resolved => Applied ==
[1003.1(2013)/Issue7+TC1 0000713]: in remquo quo should be unspecified when the result is NaN
A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=713 == Reported By:nsz Assigned To: == Project:1003.1(2013)/Issue7+TC1 Issue ID: 713 Category: System Interfaces Type: Omission Severity: Editorial Priority: normal Status: New Name: Szabolcs Nagy Organization: musl User Reference: Section:remquo Page Number: Line Number: Interp Status: --- Final Accepted Text: == Date Submitted: 2013-06-18 00:00 UTC Last Modified: 2021-11-18 16:17 UTC == Summary:in remquo quo should be unspecified when the result is NaN == -- (0005527) Don Cragun (manager) - 2021-11-18 16:17 https://austingroupbugs.net/view.php?id=713#c5527 -- WG14 voted to accept a paper yesterday that addresses this issue in C23. Since it is in alignment with that forthcoming standard, and it is existing practice, and it is "the obvious" right answer, there is a proposed resolution in bugnote 0005526. To align with the WG14 resolution, make the following change: On 2018 edition page 1814 line 58758 section remquo(), add a new paragraph after 58763: If NaN is supported and a NaN is returned, the value stored in the object pointed to by quo is unspecified. Issue History Date ModifiedUsername FieldChange == 2013-06-18 00:00 nszNew Issue 2013-06-18 00:00 nszName => Szabolcs Nagy 2013-06-18 00:00 nszOrganization => musl 2013-06-18 00:00 nszSection => remquo 2013-06-20 15:54 nick Tag Attached: c99 2021-04-14 15:01 nick Note Added: 0005312 2021-04-14 15:23 kreNote Added: 0005313 2021-04-14 15:28 kreNote Added: 0005314 2021-04-15 09:08 geoffclare Note Added: 0005317 2021-04-15 19:58 kreNote Added: 0005319 2021-04-15 19:58 kreNote Deleted: 0005313 2021-04-15 19:59 kreNote Edited: 0005319 2021-06-16 00:40 nick Note Added: 0005379 2021-06-16 08:17 Vincent LefevreNote Added: 0005380 2021-06-16 18:25 shware_systems Note Added: 0005381 2021-06-16 18:27 Don Cragun Note Added: 0005382 2021-06-16 18:28 Don Cragun Note Edited: 0005382 2021-06-16 18:30 shware_systems Note Edited: 0005381 2021-06-16 22:19 Vincent LefevreNote Added: 0005383 2021-06-17 12:30 kreNote Added: 0005384 2021-11-18 13:30 nick Note Added: 0005526 2021-11-18 16:17 Don Cragun Note Added: 0005527 ==
[1003.1(2013)/Issue7+TC1 0000713]: in remquo quo should be unspecified when the result is NaN
The following issue has been RESOLVED. == https://austingroupbugs.net/view.php?id=713 == Reported By:nsz Assigned To: == Project:1003.1(2013)/Issue7+TC1 Issue ID: 713 Category: System Interfaces Type: Omission Severity: Editorial Priority: normal Status: Resolved Name: Szabolcs Nagy Organization: musl User Reference: Section:remquo Page Number: Line Number: Interp Status: --- Final Accepted Text:See https://austingroupbugs.net/view.php?id=713#c5527. Resolution: Accepted As Marked Fixed in Version: == Date Submitted: 2013-06-18 00:00 UTC Last Modified: 2021-11-18 16:21 UTC == Summary:in remquo quo should be unspecified when the result is NaN == Issue History Date ModifiedUsername FieldChange == 2013-06-18 00:00 nszNew Issue 2013-06-18 00:00 nszName => Szabolcs Nagy 2013-06-18 00:00 nszOrganization => musl 2013-06-18 00:00 nszSection => remquo 2013-06-20 15:54 nick Tag Attached: c99 2021-04-14 15:01 nick Note Added: 0005312 2021-04-14 15:23 kreNote Added: 0005313 2021-04-14 15:28 kreNote Added: 0005314 2021-04-15 09:08 geoffclare Note Added: 0005317 2021-04-15 19:58 kreNote Added: 0005319 2021-04-15 19:58 kreNote Deleted: 0005313 2021-04-15 19:59 kreNote Edited: 0005319 2021-06-16 00:40 nick Note Added: 0005379 2021-06-16 08:17 Vincent LefevreNote Added: 0005380 2021-06-16 18:25 shware_systems Note Added: 0005381 2021-06-16 18:27 Don Cragun Note Added: 0005382 2021-06-16 18:28 Don Cragun Note Edited: 0005382 2021-06-16 18:30 shware_systems Note Edited: 0005381 2021-06-16 22:19 Vincent LefevreNote Added: 0005383 2021-06-17 12:30 kreNote Added: 0005384 2021-11-18 13:30 nick Note Added: 0005526 2021-11-18 16:17 Don Cragun Note Added: 0005527 2021-11-18 16:20 Don Cragun Note Edited: 0005527 2021-11-18 16:21 Don Cragun Interp Status => --- 2021-11-18 16:21 Don Cragun Final Accepted Text => See https://austingroupbugs.net/view.php?id=713#c5527. 2021-11-18 16:21 Don Cragun Status New => Resolved 2021-11-18 16:21 Don Cragun Resolution Open => Accepted As Marked ==
[1003.1(2013)/Issue7+TC1 0000713]: in remquo quo should be unspecified when the result is NaN
A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=713 == Reported By:nsz Assigned To: == Project:1003.1(2013)/Issue7+TC1 Issue ID: 713 Category: System Interfaces Type: Omission Severity: Editorial Priority: normal Status: New Name: Szabolcs Nagy Organization: musl User Reference: Section:remquo Page Number: Line Number: Interp Status: --- Final Accepted Text: == Date Submitted: 2013-06-18 00:00 UTC Last Modified: 2021-11-18 13:30 UTC == Summary:in remquo quo should be unspecified when the result is NaN == -- (0005526) nick (manager) - 2021-11-18 13:30 https://austingroupbugs.net/view.php?id=713#c5526 -- WG14 has voted in a paper to address this issue. See http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2790.htm. To align with this, after applying the alignment with C17 (see https://austingroupbugs.net/view.php?id=1302), make the following change: On page 1814 line 58758 section remquo(), add a new paragraph after 58763: [MX]If a NaN is returned, the value stored in the object pointed to by quo is unspecified.[/MX] Issue History Date ModifiedUsername FieldChange == 2013-06-18 00:00 nszNew Issue 2013-06-18 00:00 nszName => Szabolcs Nagy 2013-06-18 00:00 nszOrganization => musl 2013-06-18 00:00 nszSection => remquo 2013-06-20 15:54 nick Tag Attached: c99 2021-04-14 15:01 nick Note Added: 0005312 2021-04-14 15:23 kreNote Added: 0005313 2021-04-14 15:28 kreNote Added: 0005314 2021-04-15 09:08 geoffclare Note Added: 0005317 2021-04-15 19:58 kreNote Added: 0005319 2021-04-15 19:58 kreNote Deleted: 0005313 2021-04-15 19:59 kreNote Edited: 0005319 2021-06-16 00:40 nick Note Added: 0005379 2021-06-16 08:17 Vincent LefevreNote Added: 0005380 2021-06-16 18:25 shware_systems Note Added: 0005381 2021-06-16 18:27 Don Cragun Note Added: 0005382 2021-06-16 18:28 Don Cragun Note Edited: 0005382 2021-06-16 18:30 shware_systems Note Edited: 0005381 2021-06-16 22:19 Vincent LefevreNote Added: 0005383 2021-06-17 12:30 kreNote Added: 0005384 2021-11-18 13:30 nick Note Added: 0005526 ==
Re: [1003.1(2013)/Issue7+TC1 0000713]: in remquo quo should be unspecified when the result is NaN
On Thu, 17 Jun 2021 12:30:55 + Austin Group Bug Tracker via austin-group-l at The Open Group wrote: > >Summary:in remquo quo should be unspecified when the result >is NaN > This is the proposed solution to the problem you raised: http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2790.htm It has not been presented to WG14 yet (we have too many papers outstanding, so is in the queue to be discussed). --- Fred J. TydemanTydeman Consulting tyde...@tybor.com Testing, numerics, programming +1 (702) 608-6093 Vice-chair of PL22.11 (ANSI "C") Sample C99+FPCE tests: http://www.tybor.com Savers sleep well, investors eat well, spenders work forever.
[1003.1(2013)/Issue7+TC1 0000713]: in remquo quo should be unspecified when the result is NaN
A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=713 == Reported By:nsz Assigned To: == Project:1003.1(2013)/Issue7+TC1 Issue ID: 713 Category: System Interfaces Type: Omission Severity: Editorial Priority: normal Status: New Name: Szabolcs Nagy Organization: musl User Reference: Section:remquo Page Number: Line Number: Interp Status: --- Final Accepted Text: == Date Submitted: 2013-06-18 00:00 UTC Last Modified: 2021-06-17 12:30 UTC == Summary:in remquo quo should be unspecified when the result is NaN == -- (0005384) kre (reporter) - 2021-06-17 12:30 https://austingroupbugs.net/view.php?id=713#c5384 -- Re https://austingroupbugs.net/view.php?id=713#c5381 Don't be absurd, it is not this group's role to invent things (or not unless an invention is absolutely needed, which here, it definitely is not). I'll defer to those who know more about arithmetic functions if anyone cares to correct me, but my suspicion is that when the result here is a NaN, there simply is no quotient, and it makes no sense at all for the application to attempt to examine one. That's why, I'd assume, no-one has ever really been bothered by this issue, other than that what the standard says should be complete(and note that in one case, the standard already says the result is unspecified, it is just that there are other cases that were ignored - by picking a specified required value you would not just be making an editorial correction, you'd be modifying the standard). Further when different implementations do different things is not when we get to invent a solution, it is when we say the results are unspecified, which is clearly the correct thing to do here in any case. The (so far, unless things have changed) informal response from WG14 looks to be exactly what is needed, and the same language should be added here. Issue History Date ModifiedUsername FieldChange == 2013-06-18 00:00 nszNew Issue 2013-06-18 00:00 nszName => Szabolcs Nagy 2013-06-18 00:00 nszOrganization => musl 2013-06-18 00:00 nszSection => remquo 2013-06-20 15:54 nick Tag Attached: c99 2021-04-14 15:01 nick Note Added: 0005312 2021-04-14 15:23 kreNote Added: 0005313 2021-04-14 15:28 kreNote Added: 0005314 2021-04-15 09:08 geoffclare Note Added: 0005317 2021-04-15 19:58 kreNote Added: 0005319 2021-04-15 19:58 kreNote Deleted: 0005313 2021-04-15 19:59 kreNote Edited: 0005319 2021-06-16 00:40 nick Note Added: 0005379 2021-06-16 08:17 Vincent LefevreNote Added: 0005380 2021-06-16 18:25 shware_systems Note Added: 0005381 2021-06-16 18:27 Don Cragun Note Added: 0005382 2021-06-16 18:28 Don Cragun Note Edited: 0005382 2021-06-16 18:30 shware_systems Note Edited: 0005381 2021-06-16 22:19 Vincent LefevreNote Added: 0005383 2021-06-17 12:30 kreNote Added: 0005384 ==
[1003.1(2013)/Issue7+TC1 0000713]: in remquo quo should be unspecified when the result is NaN
A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=713 == Reported By:nsz Assigned To: == Project:1003.1(2013)/Issue7+TC1 Issue ID: 713 Category: System Interfaces Type: Omission Severity: Editorial Priority: normal Status: New Name: Szabolcs Nagy Organization: musl User Reference: Section:remquo Page Number: Line Number: Interp Status: --- Final Accepted Text: == Date Submitted: 2013-06-18 00:00 UTC Last Modified: 2021-06-16 22:19 UTC == Summary:in remquo quo should be unspecified when the result is NaN == -- (0005383) Vincent Lefevre (reporter) - 2021-06-16 22:19 https://austingroupbugs.net/view.php?id=713#c5383 -- But there is an issue concerning the implementations. If POSIX specifies more than ISO C, this means that C compilers used for the c99 utility would need to have a POSIX C dialect mode. Under Debian at least, c99 is a script that runs the gcc command, but GCC doesn't currently have a POSIX mode: if some code has undefined behavior in ISO C and GCC can detect this, it may consider it as dead code (or deduce some value ranges for variables), yielding incorrect code generation for POSIX C source that assumes unspecified results. Issue History Date ModifiedUsername FieldChange == 2013-06-18 00:00 nszNew Issue 2013-06-18 00:00 nszName => Szabolcs Nagy 2013-06-18 00:00 nszOrganization => musl 2013-06-18 00:00 nszSection => remquo 2013-06-20 15:54 nick Tag Attached: c99 2021-04-14 15:01 nick Note Added: 0005312 2021-04-14 15:23 kreNote Added: 0005313 2021-04-14 15:28 kreNote Added: 0005314 2021-04-15 09:08 geoffclare Note Added: 0005317 2021-04-15 19:58 kreNote Added: 0005319 2021-04-15 19:58 kreNote Deleted: 0005313 2021-04-15 19:59 kreNote Edited: 0005319 2021-06-16 00:40 nick Note Added: 0005379 2021-06-16 08:17 Vincent LefevreNote Added: 0005380 2021-06-16 18:25 shware_systems Note Added: 0005381 2021-06-16 18:27 Don Cragun Note Added: 0005382 2021-06-16 18:28 Don Cragun Note Edited: 0005382 2021-06-16 18:30 shware_systems Note Edited: 0005381 2021-06-16 22:19 Vincent LefevreNote Added: 0005383 ==
[1003.1(2013)/Issue7+TC1 0000713]: in remquo quo should be unspecified when the result is NaN
A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=713 == Reported By:nsz Assigned To: == Project:1003.1(2013)/Issue7+TC1 Issue ID: 713 Category: System Interfaces Type: Omission Severity: Editorial Priority: normal Status: New Name: Szabolcs Nagy Organization: musl User Reference: Section:remquo Page Number: Line Number: Interp Status: --- Final Accepted Text: == Date Submitted: 2013-06-18 00:00 UTC Last Modified: 2021-06-16 18:27 UTC == Summary:in remquo quo should be unspecified when the result is NaN == -- (0005382) Don Cragun (manager) - 2021-06-16 18:27 https://austingroupbugs.net/view.php?id=713#c5382 -- Re bug note:5380: I believe that you will find that the POSIX standards explicitly state when something yields undefined behavior. If the standard does not specify the behavior of some activity, the results are implicitly unspecified. Issue History Date ModifiedUsername FieldChange == 2013-06-18 00:00 nszNew Issue 2013-06-18 00:00 nszName => Szabolcs Nagy 2013-06-18 00:00 nszOrganization => musl 2013-06-18 00:00 nszSection => remquo 2013-06-20 15:54 nick Tag Attached: c99 2021-04-14 15:01 nick Note Added: 0005312 2021-04-14 15:23 kreNote Added: 0005313 2021-04-14 15:28 kreNote Added: 0005314 2021-04-15 09:08 geoffclare Note Added: 0005317 2021-04-15 19:58 kreNote Added: 0005319 2021-04-15 19:58 kreNote Deleted: 0005313 2021-04-15 19:59 kreNote Edited: 0005319 2021-06-16 00:40 nick Note Added: 0005379 2021-06-16 08:17 Vincent LefevreNote Added: 0005380 2021-06-16 18:25 shware_systems Note Added: 0005381 2021-06-16 18:27 Don Cragun Note Added: 0005382 ==
[1003.1(2013)/Issue7+TC1 0000713]: in remquo quo should be unspecified when the result is NaN
A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=713 == Reported By:nsz Assigned To: == Project:1003.1(2013)/Issue7+TC1 Issue ID: 713 Category: System Interfaces Type: Omission Severity: Editorial Priority: normal Status: New Name: Szabolcs Nagy Organization: musl User Reference: Section:remquo Page Number: Line Number: Interp Status: --- Final Accepted Text: == Date Submitted: 2013-06-18 00:00 UTC Last Modified: 2021-06-16 18:25 UTC == Summary:in remquo quo should be unspecified when the result is NaN == -- (0005381) shware_systems (reporter) - 2021-06-16 18:25 https://austingroupbugs.net/view.php?id=713#c5381 -- As this discussion is happening because the existing practice does not show a clear consensus on what value they store in &quo when NaN is the function result, I think it is in scope fpr the standard to act as referee and be inventive. To this end, as behavior end users can rely upon, I suggest tbe conforming behavior be, under Return Value: If the function is to return a NaN as result value, signalling or quiet, the value zero (0) shall be stored in &quo. I realize this is arbitrary, could use 1, INT_MIN or INT_MAX too, but until integer MaNs are required to be supported this is the cleanest resolution I see. Issue History Date ModifiedUsername FieldChange == 2013-06-18 00:00 nszNew Issue 2013-06-18 00:00 nszName => Szabolcs Nagy 2013-06-18 00:00 nszOrganization => musl 2013-06-18 00:00 nszSection => remquo 2013-06-20 15:54 nick Tag Attached: c99 2021-04-14 15:01 nick Note Added: 0005312 2021-04-14 15:23 kreNote Added: 0005313 2021-04-14 15:28 kreNote Added: 0005314 2021-04-15 09:08 geoffclare Note Added: 0005317 2021-04-15 19:58 kreNote Added: 0005319 2021-04-15 19:58 kreNote Deleted: 0005313 2021-04-15 19:59 kreNote Edited: 0005319 2021-06-16 00:40 nick Note Added: 0005379 2021-06-16 08:17 Vincent LefevreNote Added: 0005380 2021-06-16 18:25 shware_systems Note Added: 0005381 ==
[1003.1(2013)/Issue7+TC1 0000713]: in remquo quo should be unspecified when the result is NaN
A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=713 == Reported By:nsz Assigned To: == Project:1003.1(2013)/Issue7+TC1 Issue ID: 713 Category: System Interfaces Type: Omission Severity: Editorial Priority: normal Status: New Name: Szabolcs Nagy Organization: musl User Reference: Section:remquo Page Number: Line Number: Interp Status: --- Final Accepted Text: == Date Submitted: 2013-06-18 00:00 UTC Last Modified: 2021-06-16 08:17 UTC == Summary:in remquo quo should be unspecified when the result is NaN == -- (0005380) Vincent Lefevre (reporter) - 2021-06-16 08:17 https://austingroupbugs.net/view.php?id=713#c5380 -- About "the value is implicitly unspecified": AFAIK, when the standard says nothing, the behavior is implicitly undefined rather than some value being implicitly unspecified. This is much worse, because doing the operation on such arguments would be invalid, even if the value stored in &quo is never read. Issue History Date ModifiedUsername FieldChange == 2013-06-18 00:00 nszNew Issue 2013-06-18 00:00 nszName => Szabolcs Nagy 2013-06-18 00:00 nszOrganization => musl 2013-06-18 00:00 nszSection => remquo 2013-06-20 15:54 nick Tag Attached: c99 2021-04-14 15:01 nick Note Added: 0005312 2021-04-14 15:23 kreNote Added: 0005313 2021-04-14 15:28 kreNote Added: 0005314 2021-04-15 09:08 geoffclare Note Added: 0005317 2021-04-15 19:58 kreNote Added: 0005319 2021-04-15 19:58 kreNote Deleted: 0005313 2021-04-15 19:59 kreNote Edited: 0005319 2021-06-16 00:40 nick Note Added: 0005379 2021-06-16 08:17 Vincent LefevreNote Added: 0005380 ==
[1003.1(2013)/Issue7+TC1 0000713]: in remquo quo should be unspecified when the result is NaN
A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=713 == Reported By:nsz Assigned To: == Project:1003.1(2013)/Issue7+TC1 Issue ID: 713 Category: System Interfaces Type: Omission Severity: Editorial Priority: normal Status: New Name: Szabolcs Nagy Organization: musl User Reference: Section:remquo Page Number: Line Number: Interp Status: --- Final Accepted Text: == Date Submitted: 2013-06-18 00:00 UTC Last Modified: 2021-06-16 00:40 UTC == Summary:in remquo quo should be unspecified when the result is NaN == -- (0005379) nick (manager) - 2021-06-16 00:40 https://austingroupbugs.net/view.php?id=713#c5379 -- >From WG14 (as yet unofficial position from a member of the floating point subgroup): This is an issue raised by The Open Group via WG14 N2723. There are four cases where remquo() can return a NaN: remquo( NaN, y, &quo) remquo( x, NaN, &quo) remquo( infinity, y, &quo) remquo( x, 0, &quo) Only the last case (0==y) says (7.12.10.3 The remquo functions) that quo's value is unspecified. Seems like an oversite. Note: quo is an int, so cannot hold the value NaN. I suggest that words similar to: If a NaN is returned, the value stored in the object pointed to by quo is unspecified. be added to F.10.7.3 The remquo functions Issue History Date ModifiedUsername FieldChange == 2013-06-18 00:00 nszNew Issue 2013-06-18 00:00 nszName => Szabolcs Nagy 2013-06-18 00:00 nszOrganization => musl 2013-06-18 00:00 nszSection => remquo 2013-06-20 15:54 nick Tag Attached: c99 2021-04-14 15:01 nick Note Added: 0005312 2021-04-14 15:23 kreNote Added: 0005313 2021-04-14 15:28 kreNote Added: 0005314 2021-04-15 09:08 geoffclare Note Added: 0005317 2021-04-15 19:58 kreNote Added: 0005319 2021-04-15 19:58 kreNote Deleted: 0005313 2021-04-15 19:59 kreNote Edited: 0005319 2021-06-16 00:40 nick Note Added: 0005379 ==
[1003.1(2013)/Issue7+TC1 0000713]: in remquo quo should be unspecified when the result is NaN
A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=713 == Reported By:nsz Assigned To: == Project:1003.1(2013)/Issue7+TC1 Issue ID: 713 Category: System Interfaces Type: Omission Severity: Editorial Priority: normal Status: New Name: Szabolcs Nagy Organization: musl User Reference: Section:remquo Page Number: Line Number: Interp Status: --- Final Accepted Text: == Date Submitted: 2013-06-18 00:00 UTC Last Modified: 2021-04-15 19:58 UTC == Summary:in remquo quo should be unspecified when the result is NaN == -- (0005319) kre (reporter) - 2021-04-15 19:58 https://austingroupbugs.net/view.php?id=713#c5319 -- I am about to delete https://austingroupbugs.net/view.php?id=713#c5313 as I realise now that that the text I quoted is alreasy in POSIX, but only applies to the return value, not what is stored in *quot (the issue of this bug), So, just ignore that one, for anyone who ever saw it. Issue History Date ModifiedUsername FieldChange == 2013-06-18 00:00 nszNew Issue 2013-06-18 00:00 nszName => Szabolcs Nagy 2013-06-18 00:00 nszOrganization => musl 2013-06-18 00:00 nszSection => remquo 2013-06-20 15:54 nick Tag Attached: c99 2021-04-14 15:01 nick Note Added: 0005312 2021-04-14 15:23 kreNote Added: 0005313 2021-04-14 15:28 kreNote Added: 0005314 2021-04-15 09:08 geoffclare Note Added: 0005317 2021-04-15 19:58 kreNote Added: 0005319 ==
[1003.1(2013)/Issue7+TC1 0000713]: in remquo quo should be unspecified when the result is NaN
A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=713 == Reported By:nsz Assigned To: == Project:1003.1(2013)/Issue7+TC1 Issue ID: 713 Category: System Interfaces Type: Omission Severity: Editorial Priority: normal Status: New Name: Szabolcs Nagy Organization: musl User Reference: Section:remquo Page Number: Line Number: Interp Status: --- Final Accepted Text: == Date Submitted: 2013-06-18 00:00 UTC Last Modified: 2021-04-15 09:08 UTC == Summary:in remquo quo should be unspecified when the result is NaN == -- (0005317) geoffclare (manager) - 2021-04-15 09:08 https://austingroupbugs.net/view.php?id=713#c5317 -- Re: https://austingroupbugs.net/view.php?id=713#c5312 Yes it's implicitly unspecified, but that's the point. This bug is classed as editorial - it is pointing out that the wording is inconsistent in that it calls out one special case as explicitly unspecified and leaves the others as implicitly unspecified. It should either call out all of these cases explicitly or none of them. I think the reason we suggested you should refer this to the C committee is purely as a courtesy in case they want to make an editorial improvement to their wording too. Issue History Date ModifiedUsername FieldChange == 2013-06-18 00:00 nszNew Issue 2013-06-18 00:00 nszName => Szabolcs Nagy 2013-06-18 00:00 nszOrganization => musl 2013-06-18 00:00 nszSection => remquo 2013-06-20 15:54 nick Tag Attached: c99 2021-04-14 15:01 nick Note Added: 0005312 2021-04-14 15:23 kreNote Added: 0005313 2021-04-14 15:28 kreNote Added: 0005314 2021-04-15 09:08 geoffclare Note Added: 0005317 ==
[1003.1(2013)/Issue7+TC1 0000713]: in remquo quo should be unspecified when the result is NaN
A NOTE has been added to this issue.
==
https://austingroupbugs.net/view.php?id=713
==
Reported By:nsz
Assigned To:
==
Project:1003.1(2013)/Issue7+TC1
Issue ID: 713
Category: System Interfaces
Type: Omission
Severity: Editorial
Priority: normal
Status: New
Name: Szabolcs Nagy
Organization: musl
User Reference:
Section:remquo
Page Number:
Line Number:
Interp Status: ---
Final Accepted Text:
==
Date Submitted: 2013-06-18 00:00 UTC
Last Modified: 2021-04-14 15:28 UTC
==
Summary:in remquo quo should be unspecified when the result
is NaN
==
--
(0005314) kre (reporter) - 2021-04-14 15:28
https://austingroupbugs.net/view.php?id=713#c5314
--
Re https://austingroupbugs.net/view.php?id=713#c5312 -- I hate "implicitly
unspecified" - there are obviously
going to be cases (in general, not just here) where the standard says
nothing,
because no-one ever thought that there was anything to say (never realised
the
situation can occur).
But where such a case is brought to our attention, we should always be
explicit in the standard ("x is unspecified" is explicit) to avoid people
trying to read (usually invented) meaning into what is not there.
Issue History
Date ModifiedUsername FieldChange
==
2013-06-18 00:00 nszNew Issue
2013-06-18 00:00 nszName => Szabolcs Nagy
2013-06-18 00:00 nszOrganization => musl
2013-06-18 00:00 nszSection => remquo
2013-06-20 15:54 nick Tag Attached: c99
2021-04-14 15:01 nick Note Added: 0005312
2021-04-14 15:23 kreNote Added: 0005313
2021-04-14 15:28 kreNote Added: 0005314
==
[1003.1(2013)/Issue7+TC1 0000713]: in remquo quo should be unspecified when the result is NaN
A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=713 == Reported By:nsz Assigned To: == Project:1003.1(2013)/Issue7+TC1 Issue ID: 713 Category: System Interfaces Type: Omission Severity: Editorial Priority: normal Status: New Name: Szabolcs Nagy Organization: musl User Reference: Section:remquo Page Number: Line Number: Interp Status: --- Final Accepted Text: == Date Submitted: 2013-06-18 00:00 UTC Last Modified: 2021-04-14 15:01 UTC == Summary:in remquo quo should be unspecified when the result is NaN == -- (0005312) nick (manager) - 2021-04-14 15:01 https://austingroupbugs.net/view.php?id=713#c5312 -- If the standard says nothing about this case (which it doesn't), then the value is implicitly unspecified. Issue History Date ModifiedUsername FieldChange == 2013-06-18 00:00 nszNew Issue 2013-06-18 00:00 nszName => Szabolcs Nagy 2013-06-18 00:00 nszOrganization => musl 2013-06-18 00:00 nszSection => remquo 2013-06-20 15:54 nick Tag Attached: c99 2021-04-14 15:01 nick Note Added: 0005312 ==
