Re: failure due to compiler?

WStreett@shell.monmouth.com (Wilbur Streett)
13 Jul 1996 17:00:57 -0400

          From comp.compilers

Related articles
[4 earlier articles]
failure due to compiler? flake@elda.demon.co.uk (1996-07-09)
Re: failure due to compiler? dennis@netcom.com (1996-07-10)
Re: failure due to compiler? dennis@netcom.com (1996-07-10)
Re: failure due to compiler? grout@polestar.csrd.uiuc.edu (1996-07-10)
Re: failure due to compiler? khays@sequent.com (1996-07-10)
Re: failure due to compiler? cliffc@ami.sps.mot.com (1996-07-10)
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)
[18 later articles]
| List of all articles for this month |
From: WStreett@shell.monmouth.com (Wilbur Streett)
Newsgroups: comp.compilers
Date: 13 Jul 1996 17:00:57 -0400
Organization: Monmouth Internet Corporation
References: 96-07-041 96-07-056
Keywords: errors

>|> I am looking for pointers or references to descriptions where software
>|> has compiled without error and later failed due to compiler-introduced
>|> errors in the resultant program. In other words, the source was deemed
>|> to be error free but the compiler botched the code generation.


What about when the compiler tells you that there is an error in the code
but there isn't? (and of course the error message should include the line
number, but it doesn't?) It of course only randomly does this every 4th or
so compile? Would that qualify as an error of the sort that you are
looking for?


Wilbur


--


Post a followup to this message

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