From: Doug McIlroy <doug@cs.dartmouth.edu>
To: tuhs@tuhs.org
Subject: Re: [TUHS] DEC Compilers (was: Re: SDB debugger
Date: Wed, 06 May 2020 11:53:50 -0400 [thread overview]
Message-ID: <202005061553.046FroWn099876@tahoe.cs.Dartmouth.EDU> (raw)
>> 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.
Doug
next reply other threads:[~2020-05-06 15:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-06 15:53 Doug McIlroy [this message]
2020-05-06 20:21 ` Tim Rylance
-- 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=202005061553.046FroWn099876@tahoe.cs.Dartmouth.EDU \
--to=doug@cs.dartmouth.edu \
--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).