Related articles |
---|
[10 earlier articles] |
Re: failure due to compiler? WStreett@shell.monmouth.com (1996-07-13) |
Re: failure due to compiler? jfc@mit.edu (1996-07-13) |
Re: failure due to compiler? bobduff@world.std.com (1996-07-13) |
Re: failure due to compiler? baynes@ukpsshp1.serigate.philips.nl (1996-07-13) |
Re: failure due to compiler? alain@phidani.be (Corchia Alain) (1996-07-15) |
Re: failure due to compiler? dave_sc@csl.sri.com (1996-07-15) |
Re: failure due to compiler? kanze@lts.sel.alcatel.de (1996-07-16) |
Re: failure due to compiler? glew@ichips.intel.com (1996-07-16) |
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) |
[12 later articles] |
From: | kanze@lts.sel.alcatel.de (James Kanze US/ESC 60/3/141 #40763) |
Newsgroups: | comp.compilers |
Date: | 16 Jul 1996 08:15:41 -0400 |
Organization: | GABI Software, Sarl. |
References: | 96-07-041 96-07-079 |
Keywords: | errors |
bobduff@world.std.com (Robert A Duff) writes:
|> Yes, compilers have bugs. I've seen many. What would be more
|> interesting (to me, anyway) would be cases where compiler bugs actually
|> caused some real damage. E.g. so-and-so plane crashed because of a
|> compiler bug, and killed so-and-so number of people. Or so-and-so
|> company lost $100,000 because of a compiler bug. Or some such thing.
I imagine that a company losing $100.000 is actually fairly frequent.
I'm sure, for example, that we've lost more than that at my present
customer site due to compiler bugs. It usually takes at least a week of
debugging to determine that it is a compiler bug, and another week to
find a work-around. Then someone else falls into the same case, except
that it looks different superficially. In almost no time, on a large
project, you'll find that you've spent a man-year. And a man-year comes
out to about $100.000 (or a little more).
Even when you know the bug is there, it costs. Every time you come up
with a new design, someone has to spend time verifying that it isn't
going to run up against the bug. Sometimes, you end up adapted
definitly inferior designs just because you know they don't exercise the
buggy part of the compiler.
--
James Kanze Tel.: (+33) 88 14 49 00 email: kanze@gabi-soft.fr
GABI Software, Sarl., 8 rue des Francs-Bourgeois, F-67000 Strasbourg, France
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.