9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] Compiling ken-cc on Linux
Date: Sun, 29 Nov 2015 08:12:41 +0200	[thread overview]
Message-ID: <96df9ced9a56f62ae0d46b0692093cc6@proxima.alt.za> (raw)
In-Reply-To: <4BA8023A-95EF-4B39-85E2-444DD2766C61@me.com>

> One interesting thing is that for the past twenty years new
> architectures have been designed to run C code well.  Just check out
> the papers a ISCA.  Then why do we have to have such complicated
> compilers to generate code for it.

I'm pretty sure that you can lay that at C's door.  Had Algol or
Pascal been targeted, the architectures would not have so many
loopholes to go insane over.  C's pragmatism came back to bite it.

Of course, Algol or Pascal's discipline meant they never stood a
chance, so it's a lose-lose situation.  Let's be grateful that C
existed at all.  Had ADA or PL/I won that war, I doubt the Personal
Computer would have ever become affordable.

What it suggests to me is that the next programming notation should
first of all describe an architecture that can be engineered without
an infinite array of corner cutting features that can't be represented
in any semblance of programming code, which is why the compiler needs
to know about each and every one and even the likely circumstances
under which they ought to be used.

Then we can hand to the engineers a programming language they can
target with their architectures and they won't botch it too badly.

On further thought, it's obvious where it all went wrong: C is not one
language, it is only scaffolding.  Targeting it was bound to lead to
an infinite number of outcomes.

Lucio.




  reply	other threads:[~2015-11-29  6:12 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-28  6:42 da Tyga
2015-11-28  7:40 ` Brantley Coile
2015-11-28 20:31   ` Anthony Sorace
2015-11-28 23:33     ` Brantley Coile
2015-11-29  6:12       ` lucio [this message]
2015-11-28 20:13 ` Ryan Gonzalez
2015-11-29  5:57   ` lucio
2015-11-29 16:17     ` tlaronde
  -- strict thread matches above, loose matches on Subject: below --
2015-11-25 17:10 Vasudev Kamath
2015-11-25 17:15 ` Ryan Gonzalez
2015-11-25 17:24   ` Vasudev Kamath
2015-11-26 12:08     ` Charles Forsyth
2015-11-27 16:50   ` Vasudev Kamath
2015-11-27 16:59     ` Ryan Gonzalez
2015-11-27 17:16       ` Vasudev Kamath
2015-11-27 18:24         ` Ryan Gonzalez
2015-11-29  9:41           ` Vasudev Kamath
2015-11-29 14:38             ` Ryan Gonzalez
2015-11-27 18:11   ` trebol
2015-11-26 12:10 ` Charles Forsyth
2015-11-26 12:18   ` David du Colombier
2015-11-26 18:15   ` Ryan Gonzalez
2015-11-26 21:31     ` Charles Forsyth
2015-11-26 21:49       ` Ryan Gonzalez
2015-11-26 21:51         ` Charles Forsyth
2015-11-26 21:56           ` Charles Forsyth
2015-11-26 22:02             ` Ryan Gonzalez
2015-11-26 22:08               ` Charles Forsyth
2015-11-26 22:30                 ` David du Colombier
2015-11-26 23:08                   ` Ryan Gonzalez
2015-11-26 23:21                     ` Charles Forsyth
2015-11-26 23:41                       ` Ryan Gonzalez
2015-11-27  0:02                       ` Brantley Coile
2015-11-27  8:13                       ` Giacomo Tesio
2015-11-27  8:56                         ` arnold
2015-11-27 13:33                           ` Steffen Nurpmeso
2015-11-28  0:55                             ` erik quanstrom
2015-11-30 15:46                               ` Steffen Nurpmeso
2015-11-27 12:42                         ` tlaronde
2015-11-27 14:07                           ` Giacomo Tesio
2015-11-27 14:34                             ` tlaronde
2015-11-28  1:01                             ` erik quanstrom
2015-11-27 12:05                       ` Steffen Nurpmeso
2015-11-27 12:32       ` lucio
2015-11-26 21:40     ` Andrew Simmons

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=96df9ced9a56f62ae0d46b0692093cc6@proxima.alt.za \
    --to=lucio@proxima.alt.za \
    --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).