From mboxrd@z Thu Jan  1 00:00:00 1970
To: 9fans@cse.psu.edu
Subject: Re: [9fans] GUI toolkit for Plan 9
From: anothy@cosym.net
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Message-Id: <20020304133718.F160019A7D@mail.cse.psu.edu>
Date: Mon,  4 Mar 2002 08:35:49 -0500
Topicbox-Message-UUID: 5e69dc74-eaca-11e9-9e20-41e7f4b1d025

// So far I know of one optimization bug in the 8c compiler
// and none in GCC.  Do you have some you know about but
// aren't reporting?

being a very infrequent user of gcc, and having no emotional
energy invested it its status, i've not been keeping lists of any
strange doings, nor even looking into them fully to determine
whether they're bugs or no. however, a quick google turns up
lots and lots of responses for various queries on gcc optimizer
bugs. further, curious as to what the official bug repository for
gcc bugs is, i wandered over to gcc.gnu.org and noticed they
have an gnats db there. a quick search for non-closed optim.
bugs returns 156 results (the majority of which are in the open
state). that says nothing of previous ones which have been
fixed. given the probability of duplication of bug reports or
people simply being wrong, i imagine the real number is much
lower than 156, but substantially above 1.

i am not an expert on the formal definitions of C, but the code
rob (from rsc?) posted earlier certainly seemed reasonable (i'm
refering to the x=sqrt(3.0) stuff). can someone confirm?
ア