From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Tue,  1 Dec 2009 17:31:23 -0500
To: 9fans@9fans.net
Message-ID: <46d4fa4852db88ca9609ab3b42b84723@ladd.quanstro.net>
In-Reply-To: <<d893fc0b1d0b52a1dd610d7eb14279d3@terzarima.net>>
References: <<d893fc0b1d0b52a1dd610d7eb14279d3@terzarima.net>>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] compiler double bug.
Topicbox-Message-UUID: a683cdf2-ead5-11e9-9d60-3106f5b1d025

> so getival returning uint or ulong (or unsigned something-big-enough) avoids
> the problem and seems fine to me.

good.  i always get diff backwards.  sorry.
i agree on the standard quite.

> there is, however, a bug in the compiler elsewhere, in that a suitable (uint) cast in a
> direct assignment
> 	int x = (uint)doubleval;
> is (apparently) discarded by the compiler, and it shouldn't be.
> that shouldn't affect your getival cases, though.

the implicit conversion on return also appears botched.

- erik