Re: failure due to compiler?

gah@u.washington.edu (G. Herrmannsfeldt) wrote:


<snip>


>1) A C compiler that miscompiled double a; a++;
> I don't remember what it did, but I checked (comp.lang.c) and ++ is legal
> on double.


I remember that I once saw some generated code that did an inc operation
on the lower half of a double only.. it assumed that the a++ operation
was specifically an interger operation and simply generated an ASM INC
instruction. It was either Lattice C in the dark ages or Microsoft C more
than 5 years ago.


Speaking of problems with compilers, I can remember that I was asked to
port all of my code for a project that was shipping the next day from
Borland C to IBM Visual Age C++. The compiler documentation said that
allocating memory in the large model MAY produce a pointer to valid
memory, or it may produce a pointer that would wrap around in a segment.
Given that the documentation used the word "MAY", I stayed very far away
from all of their memory allocation routines.


Right now I'm playing with MSVC 4.0 and it keeps telling me that the
project files are out of date whenever I execute in Debug mode, even
though I just completed a build. Really builds confidence.


Wilbur


--

Return to the comp.compilers page.
Search the comp.compilers archives again.