From: "John P. Linderman" <jpl.jpl@gmail.com>
To: Paul Winalski <paul.winalski@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Disassemblers
Date: Fri, 2 Jul 2021 14:07:27 -0400 [thread overview]
Message-ID: <CAC0cEp97xCsK8XKd1pZNp8FU0J2w4eZSWvn9w0rO32mMLfvgtA@mail.gmail.com> (raw)
In-Reply-To: <CABH=_VSNzWW57TuufHnDFsgvCN=WZfr8G9PWDxLz4ddVVnJOcg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2148 bytes --]
On a related (optimization) theme,
https://research.swtch.com/hwmm
On Fri, Jul 2, 2021 at 12:58 PM Paul Winalski <paul.winalski@gmail.com>
wrote:
> I sent a reply to this message to the TUHS mailing list but gmail may
> have rejected it and flagged it as spam.
>
> Please email me privately to let me know if the message made it to the
> list.
>
> -Paul W..
>
> On 7/1/21, scj@yaccman.com <scj@yaccman.com> wrote:
> > I saw this post and it reminded me of a meeting that Dennis and I had
> > with Bill Wulf. At one point, Dennis decided to write an optimizer but
> > gave up after a week or two because when he had coded the data
> > structures he needed he had filled up the PDP-11 memory! It was a very
> > strong part of the Unix meme that Unix and C would run on small
> > computers since most of the universities couldn't afford bigger ones at
> > the time.
> >
> > When PCC came along and started running on 32-bit machines, I started
> > thinking about algorithms for optimization. A problem that I had no
> > good solution for could be illustrated by a simple piece of code:
> >
> > x = *p;
> >
> > y = *q;
> >
> > q gets changed
> >
> > *q = z;
> >
> > The question is, do I need to reload x now because q might have been
> > changed to point to the same place as p? At around this time, Al Aho
> > was invited to go to CMU and give a talk, and he invited me to come with
> > him. We spent about an hour and a half one-on-one with Bill Wulf -- I
> > seem to remember a lot of mutual respect going on. But when I asked him
> > about my problem, he really didn't have much to say about it. I finally
> > got him to agree that his compiler had a bug. But he said there was a
> > flag they could set on the compiler that would turn of optimization and
> > if your program had mysterious bugs, you should use the flag.
> >
> > I recall that Al, always in search of better algorithms, was a bit
> > disappointed -- I was a bit more pragmatic about it. On the whole, it
> > was a good meeting, and the "Engineering ... Compiler" book was one of
> > my favorites when it came out.
> >
> > Steve
>
[-- Attachment #2: Type: text/html, Size: 3054 bytes --]
next prev parent reply other threads:[~2021-07-02 18:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-19 15:04 Henry Bent
2021-06-19 15:54 ` Clem Cole
2021-06-19 16:33 ` Henry Bent
2021-06-19 16:59 ` Clem Cole
2021-06-19 20:44 ` Richard Salz
2021-06-19 21:49 ` Rob Pike
2021-06-19 21:50 ` Rob Pike
2021-06-19 22:55 ` Clem Cole
2021-06-19 23:14 ` Larry McVoy
2021-06-20 1:41 ` Brantley Coile
2021-07-02 1:36 ` scj
2021-07-02 16:56 ` Paul Winalski
2021-07-02 17:45 ` Paul Winalski
2021-07-02 18:07 ` John P. Linderman [this message]
2021-06-19 17:57 Noel Chiappa
2021-06-19 18:40 ` Clem Cole
2021-06-20 1:15 Norman Wilson
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=CAC0cEp97xCsK8XKd1pZNp8FU0J2w4eZSWvn9w0rO32mMLfvgtA@mail.gmail.com \
--to=jpl.jpl@gmail.com \
--cc=paul.winalski@gmail.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).