From: Chris McGee <newton688@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Is Plan 9 C "Less Dangerous?"
Date: Tue, 4 Sep 2018 22:29:24 -0400 [thread overview]
Message-ID: <CAOk9ws1fTVCHWFVk1bcmTiP7DyBm=TD0xPoSnyaYoFtv9EPUWQ@mail.gmail.com> (raw)
In-Reply-To: <CALj3Nd1ax8rsBcVM3jveMx57+f6i_nv=U4VapjG06yKsVN=iZQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 918 bytes --]
> I believe that the core of the problem with the C language is that is
> based upon abstracting the PDP-11 instruction set. CPUs, such as Intel/AMD
> x64 are vastly more complex so "optimising" C compilers are trying to make
> something simple take advantage of something far more complex. Perhaps we
> should call them "complexifying" compilers.
>
> Generally, model-to-model transformations (which is effectively what
> compilers do under the covers) are easier to define when we transform from
> a higher level of abstraction to a lower level of abstraction. As folks in
> the MBSE field explain it, trying to put a pig together from sausages.
>
I wonder if the hardware world suffers from some of the same complexity
problems the software world does. Is it possible to build much simpler
hardware as well or are there real physical properties that force them to
be as complex as they are now?
[-- Attachment #2: Type: text/html, Size: 1160 bytes --]
next prev parent reply other threads:[~2018-09-05 2:29 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-02 16:31 Chris McGee
2018-09-02 16:52 ` hiro
2018-09-03 4:07 ` Lucio De Re
2018-09-03 12:40 ` Chris McGee
2018-09-03 17:58 ` Ethan Gardener
2018-09-04 10:51 ` Lucio De Re
2018-09-04 11:33 ` Ethan Gardener
2018-09-04 11:41 ` Chris McGee
2018-09-02 18:16 ` Lucio De Re
2018-09-02 19:18 ` Steve Simon
2018-09-02 19:21 ` Iruatã Souza
2018-09-03 1:03 ` Charles Forsyth
2018-09-03 2:03 ` Skip Tavakkolian
2018-09-04 23:17 ` Charles Forsyth
2018-09-04 23:30 ` Tyga
2018-09-05 2:29 ` Chris McGee [this message]
2018-09-05 11:23 ` Dave MacFarlane
2018-09-05 11:42 ` Chris McGee
2018-09-05 13:35 ` Ethan Gardener
2018-09-05 15:38 ` Iruatã Souza
2018-09-05 23:59 ` Chris McGee
2018-09-06 0:32 ` Bakul Shah
2018-09-06 3:40 ` Lucio De Re
2018-09-06 11:41 ` Chris McGee
2018-09-06 13:37 ` Ethan Gardener
2018-09-06 17:48 ` Richard Miller
2018-09-06 19:08 ` Skip Tavakkolian
2018-09-06 21:21 ` Chris McGee
2018-09-07 8:32 ` Richard Miller
2018-09-05 3:25 ` Ori Bernstein
2018-09-05 8:19 ` Ethan Gardener
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='CAOk9ws1fTVCHWFVk1bcmTiP7DyBm=TD0xPoSnyaYoFtv9EPUWQ@mail.gmail.com' \
--to=newton688@gmail.com \
--cc=9fans@9fans.net \
/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).