Re: failure due to compiler?

WStreett@shell.monmouth.com (Wilbur Streett)
20 Jul 1996 21:38:26 -0400

          From comp.compilers

Related articles
[18 earlier articles]
Re: failure due to compiler? WStreett@shell.monmouth.com (1996-07-16)
Re: failure due to compiler? grout@polestar.csrd.uiuc.edu (1996-07-18)
Re: failure due to compiler? gah@u.washington.edu (1996-07-19)
Re: failure due to compiler? ok@cs.rmit.edu.au (1996-07-20)
Re: failure due to compiler? LEEW@FS.MICROLOGIC.COM (Lee Webber) (1996-07-20)
Re: failure due to compiler? iwm@doc.ic.ac.uk (Ian Moor) (1996-07-20)
Re: failure due to compiler? WStreett@shell.monmouth.com (1996-07-20)
Re: failure due to compiler? jgllgher@maths.tcd.ie (Dara Gallagher) (1996-07-20)
Re: failure due to compiler? ok@cs.rmit.edu.au (1996-07-22)
Re: failure due to compiler? rfg@monkeys.com (1996-07-22)
Re: failure due to compiler? leew@micrologic.com (Lee Webber) (1996-07-23)
Re: failure due to compiler? eric@gyst.com (Eric Hamilton) (1996-07-23)
Re: failure due to compiler? davidg@genmagic.com (1996-07-23)
[4 later articles]
| List of all articles for this month |

From: WStreett@shell.monmouth.com (Wilbur Streett)
Newsgroups: comp.compilers
Date: 20 Jul 1996 21:38:26 -0400
Organization: Monmouth Internet Corporation
References: 96-07-041 96-07-056 96-07-064 96-07-079 96-07-100 96-07-123
Keywords: errors

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


--


Post a followup to this message

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