From: | ArarghMail809@Arargh.com |
Newsgroups: | comp.compilers |
Date: | Wed, 24 Sep 2008 14:31:05 -0500 |
Organization: | Ripco Communications Inc. |
References: | 08-09-076 08-09-105 08-09-110 08-09-115 08-09-119 |
Keywords: | debug |
Posted-Date: | 24 Sep 2008 15:51:39 EDT |
On Wed, 24 Sep 2008 12:46:15 -0400, Chris F Clark
<cfc@shell01.TheWorld.com> wrote:
<snip>
>So, I wonder, how many of you have experienced real compiler bugs,
>that you could verify was the compilers fault and not just "mysterious
>behavior" that could be fixed by changing the optimizer/debugger
>level?
It's been a while, but I have. It was the Microsoft Basic Compiler
Version 6 (The one between QB4.5 & PDS). Someone else & I spent about
a week isolating the problem and developing a small program that
showed the error. It worked on the previous version, and failed on
version 6. It was reported to MS and that's the last we ever heard.
And, of course, there is the well known bug in MASM 6:
...
.data? (.bss space - not initialized)
foo db 500000 dup (?)
...
Works, but takes forever. :-) But that's an assembler. :-)
As well as any bugs in BCET, but that's my problem. :-)
--
ArarghMail809 at [drop the 'http://www.' from ->] http://www.arargh.com
BCET Basic Compiler Page: http://www.arargh.com/basic/index.html
To reply by email, remove the extra stuff from the reply address.
Return to the
comp.compilers page.
Search the
comp.compilers archives again.