Related articles |
---|
[17 earlier articles] |
Re: binary search debugging of compilers 864-117-4973@kylheku.com (Kaz Kylheku) (2023-05-19) |
Re: binary search debugging of compilers 864-117-4973@kylheku.com (Kaz Kylheku) (2023-05-19) |
binary search debugging of compilers cclick0@gmail.com (Cliff Click) (2023-05-19) |
binary search debugging of compilers tekk.nolagi@gmail.com (Max B) (2023-05-19) |
Re: binary search debugging of compilers tkoenig@netcologne.de (Thomas Koenig) (2023-05-19) |
Re: binary search debugging of compilers mrs@kithrup.com (2023-05-20) |
Re: binary search debugging of compilers gah4@u.washington.edu (gah4) (2023-05-20) |
Re: Old C compilers, binary search debugging of compilers DrDiettrich1@netscape.net (Hans-Peter Diettrich) (2023-05-22) |
From: | gah4 <gah4@u.washington.edu> |
Newsgroups: | comp.compilers |
Date: | Sat, 20 May 2023 20:20:56 -0700 (PDT) |
Organization: | Compilers Central |
References: | 23-05-003 23-05-005 23-05-006 23-05-008 23-05-011 23-05-012 23-05-015 23-05-017 23-05-020 23-05-025 |
Injection-Info: | gal.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="38487"; mail-complaints-to="abuse@iecc.com" |
Keywords: | debug, history |
Posted-Date: | 21 May 2023 14:25:53 EDT |
In-Reply-To: | 23-05-025 |
On Saturday, May 20, 2023 at 3:05:13 PM UTC-7, Thomas Koenig wrote:
> Kaz Kylheku <864-11...@kylheku.com> schrieb:
> > Oh, stepping doubles with ++ is, I would say, not *that* uncommon.
> > I doubt that if such a bug were introduced as an easter egg into GCC,
> > it would go very long without being discovered by the FOSS distros and
> > other downstream users.
> It would very likely be caught by regression testing. GCC has an
> extensive test suite, and it is a requirement that this is run
> before submitting a patch.
I believe it was Borland Turbo C, maybe 2.0.
At one point, I had a few different C compilers for MS-DOS, not so long
before I went to using OS/2. It seems that Borland also had compilers
for OS/2, but I don't remember using those.
Return to the
comp.compilers page.
Search the
comp.compilers archives again.