9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "AMSRL-CI-CN" <gwyn@arl.army.mil>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] compilers - was GUI toolkit for Plan 9
Date: Thu, 28 Feb 2002 15:11:13 +0000	[thread overview]
Message-ID: <Gs8zr9.I7F@arl.army.mil> (raw)
In-Reply-To: <200202270021.g1R0L0s43681@ducky.net>

"Mike Haertel" <mike@ducky.net> wrote in message
news:200202270021.g1R0L0s43681@ducky.net...
> The idea that "hardware/software co-design" is Good has to rank
> among the great fallacies of computer science and the computing
> industry in the last two decades.

Unfortunately, performance expectations for new processors require
rather complex architectures involving multiple concurrent pipelines,
etc. making efficient use of the architectures difficult; therefore more
responsibility is placed on the code generators.  This seems inevitable.
There are C compilers whose "code" is actually gate configurations
for FPGAs, etc. which is of course this idea taken to an extreme.

In earlier days of computing, little attention was usually paid to the
requirements of HLLs when designing ISAs, and sometimes what
the IS architects guessed would be helpful really wasn't (e.g. PDP-11
MARK instruction).  (There were a few notable exceptions, e.g.
Burroughs [56][57]00 models.)  The result was that major parts of
processors were not used at all by HLLs, which was bad economics.
This lack of input from compiler developers was widely recognized,
and by the early 1980s several processor manufacturers had changed
their procedures so that the hardware guys and compiler guys talked
to each other early enough to influence the design (of both).

These days, it is generally assumed that most programming is going
to be in C, so attention is focussed on supporting C to the possible
detriment of other languages..

> However they might curse the oddities of the x86 ISA, I am sure the
> Plan 9 developers are grateful for the fact that all x86 implementations
> are designed with a goal of getting at least adeqaute performance
> without recompiling.

?  Intel's x86 architecture was designed to be used from assembly
language, not HLL, and it is pretty bad when judged by its support
for HLLs.  Even the more recent MMX etc. extensions aren't well
suited for use from HLLs except via machine-specific asm hooks.


  reply	other threads:[~2002-02-28 15:11 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-26 20:28 [9fans] " presotto
2002-02-26 21:34 ` [9fans] compilers - was " Matt H
2002-02-26 22:06   ` Theo Honohan
2002-02-27  0:21   ` Mike Haertel
2002-02-28 15:11     ` AMSRL-CI-CN [this message]
2002-02-28 16:55       ` Thomas Bushnell, BSG
2002-02-27  6:54 ` [9fans] " Eric Dorman
2002-02-27 10:20   ` Thomas Bushnell, BSG
2002-02-27 10:51     ` Lucio De Re
2002-02-27 13:27       ` Boyd Roberts
2002-02-27 14:20       ` Ish Rattan
2002-02-27 22:44       ` Thomas Bushnell, BSG
2002-02-28  4:41         ` Lucio De Re
2002-02-28 10:19           ` Thomas Bushnell, BSG
2002-02-28 10:14       ` Thomas Bushnell, BSG
2002-02-28 10:49         ` Matt H
2002-03-01 13:25           ` chad
2002-02-28  3:26     ` [9fans] GUI toolkit for Plan 9 [really GPL again!] Eric Dorman
2002-02-28  9:57     ` [9fans] GUI toolkit for Plan 9 ozan s yigit
2002-02-28 14:55 ` AMSRL-CI-CN
2002-02-26 22:17 [9fans] compilers - was " jmk
2002-02-27  2:38 Russ Cox
2002-02-27  9:28 Bengt Kleberg

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=Gs8zr9.I7F@arl.army.mil \
    --to=gwyn@arl.army.mil \
    --cc=9fans@cse.psu.edu \
    /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).