On Thu, 13 Sep 2018, Andrew Josey wrote:
Bug 0001133: find clarification on -xdev behavior for mounted filesystem within
primary OPEN
http://austingroupbugs.net/view.php?id=1133
We discussed this item. We believe that the current wording in the standard
requires mount points to be included
On Mon, 29 Jan 2018, Nick Stoughton wrote:
Statement [1] is about granularity ... if the implementation, for example,
only handles 1 second timestamp resolution, then the effect of futimesns()
is to truncate the time by ignoring the tv_nsec portion ... it must not
attempt to round up the value.
On Mon, 18 Dec 2017, I wrote:
...
Example: if y = DBL_MIN and x = 2, then y/x underflows to DBL_MIN/2,
but the infinite-precision result for atan2(x, y) is slightly larger,
so in round-towards-plus-infinity mode the result should never be y/x,
but must larger. How much larger? About
On Sun, 17 Dec 2017, Austin Group Bug Tracker wrote:
Summary:atan2: Description of IEC 60559 Floating-Point
option is unclear
Description:
What is meaning of the following statement:
If the IEC 60559 Floating-Point option is supported, y/ x should be
returned.
This is
On Thu, 9 Nov 2017, Hal Finkel wrote:
Forwarded Message
...
From Jim Thomas. I???ll leave it to you to forward this to Austin Group.
Hal is correct, and I think the response to him misses the
point that he raised.
Agreed.
What Hal was talking about was the fact
On Thu, 9 Nov 2017, Joseph Myers wrote:
On Thu, 9 Nov 2017, Hal Finkel wrote:
Thus, neither cabs, nor most other math.h/complex.h functions taking
floating-point inputs and producing a floating-point output, should ever
formally overflow (because even infinity lies within the represented
On Wed, 8 Nov 2017, Joseph Myers wrote:
On Wed, 8 Nov 2017, Bruce Evans wrote:
This is without Annex F (IEEE754/IOCmumble bindings). With Annex F,
Actually Annex G (F is for plain floating point types and G is for complex
floating point types).
cabs() is specified in terms of hypot
On Tue, 7 Nov 2017, Hal Finkel wrote:
My reading of the combined C and POSIX specifications leads me to believe
that functions in complex.h don't set errno on POSIX systems. This came up
recently during a code review for the Clang compiler [1]. It has been pointed
out that, under glibc,
