From: Tim Rylance <tuhs@tkr.bondplaza.com>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] DEC Compilers (was: Re: SDB debugger
Date: Wed, 6 May 2020 21:21:08 +0100 [thread overview]
Message-ID: <108B38F3-B0E0-46D3-A78F-0A7CE57C6EEB@tkr.bondplaza.com> (raw)
In-Reply-To: <202005061553.046FroWn099876@tahoe.cs.Dartmouth.EDU>
[-- Attachment #1: Type: text/plain, Size: 1570 bytes --]
>>> Compile time was measured. My favorite "bug" was the
>>> many minutes it took to compile a constant expression
>>> that involved shifting a constant INT_MAX bits by
>>> performing that many 1-bit shifts.
>>
>> I don't know if this anecdote is an urban legend or if it really
>> happened. I was told [a similar] story when I was interning as an operator
>> at my alma mater, which was an IBM System/360 shop.
>
> I heard it not from the grapevine, but from McKeeman himself.
It’s mentioned in the paper (https://www.hpl.hp.com/hpjournal/dtj/vol10num1/vol10num1art9.pdf <https://www.hpl.hp.com/hpjournal/dtj/vol10num1/vol10num1art9.pdf>) on page 105, table 1
Results of Testing C Compilers
Source Code Resulting Problem
1>>INT_MAX Twenty-minute compile time
but not explained.
My favourite is
int(…(x)…) enough nested parentheses to kill the compiler
Spurious diagnostic (10 parentheses)
Compiler crash (100 parentheses)
Server crash (10,000 parentheses)
explained on page 104:
… the server crash occurred when the tested compiler got a stack overflow on a heavily loaded machine with a very large memory. The operating system attempted to dump a gigabyte of compiler stack, which caused all the other active users to thrash, and many of them also dumped for lack of memory. The many disk drives on the server began a dance of the lights that sopped up the remaining free resources, causing the operators to boot the server to recover. Excellent testing can make you unpopular with almost everyone.
[-- Attachment #2: Type: text/html, Size: 2960 bytes --]
next prev parent reply other threads:[~2020-05-06 20:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-06 15:53 Doug McIlroy
2020-05-06 20:21 ` Tim Rylance [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-05-06 2:52 Doug McIlroy
2020-05-01 20:48 [TUHS] " Paul Ruizendaal
2020-05-02 0:49 ` Noel Hunt
2020-05-02 20:16 ` Paul Ruizendaal
2020-05-03 16:13 ` Clem Cole
2020-05-03 17:13 ` Henry Bent
2020-05-03 20:26 ` Clem Cole
2020-05-05 0:22 ` [TUHS] DEC Compilers (was: " Win Treese
2020-05-05 17:36 ` Paul Winalski
2020-05-05 18:53 ` Dr Iain Maoileoin
2020-05-05 21:59 ` Dan Cross
2020-05-05 21:49 ` Henry Bent
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=108B38F3-B0E0-46D3-A78F-0A7CE57C6EEB@tkr.bondplaza.com \
--to=tuhs@tkr.bondplaza.com \
--cc=tuhs@tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).