From: tlaronde@polynum.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] NUMA
Date: Sun, 17 Jul 2011 18:37:57 +0200 [thread overview]
Message-ID: <20110717163757.GA1564@polynum.com> (raw)
In-Reply-To: <b2ea5af04a782a917218b30b26ebff3e@ladd.quanstro.net>
On Sun, Jul 17, 2011 at 11:51:04AM -0400, erik quanstrom wrote:
> [...]
>
> iirc, almost all isa -> µop translations are handled
> by hardware for intel. i shouldn't be so lazy and look this up
> again.
>From what I read, IIRC (for example in Hennessy and Patterson, some
years ago), even the x86 family has RISC underneath.
>
> >
> > I have an example with gcc4.4, compiling not my source, but D.E.K.'s
> > TeX.
>
> i think you're mixing apples and oranges. gcc has nothing to do with
> whatever is running inside a procesor, microcode or not.
It is an illustration of the result of complexity, not a direct match to
hardware.
This is the evolution that is becoming worrying.
At the beginning, programmers were directly programming the machine.
Since it was a pain, some assembly languages were born; but their
symbolic and almost macro-definition kind made a direct translation
so an easy guarantee. This is definitively not the case anymore
with something in between that does more and more complex (and
hidden) things: the compiler set.
Languages are more and more "high level" that is far from the hardware.
The hardware is more and more complex and not pure hardware.
The result of a "story" (the source) written by someone (programmer) who
does not know exactly what he says; with a compiler that does not tell
what it does; feeding a hardware that can not guarantee it will do
exactly what it's told to, this result is not, shall we say, soothing.
I know that english speaking culture is fond of mystery and magics
(from Shakespeare to Harry Potter; Lord of the Rings to Batman and so
on). And perhaps the "Red Dragon" book about compiler is meant precisely
to emphasize that programming is kind of some Arthurian initiation,
fighting amidst the fog. But my french cartesian brains are not a
perfect match for this ;)
--
Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
http://www.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
next prev parent reply other threads:[~2011-07-17 16:37 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-15 15:15 tlaronde
2011-07-15 20:21 ` tlaronde
2011-07-15 20:47 ` ron minnich
2011-07-15 22:59 ` Charles Forsyth
2011-07-16 8:02 ` tlaronde
2011-07-16 16:27 ` erik quanstrom
2011-07-16 18:06 ` tlaronde
2011-07-16 19:29 ` Ethan Grammatikidis
2011-07-16 19:54 ` erik quanstrom
2011-07-16 20:56 ` dexen deVries
2011-07-16 22:10 ` Charles Forsyth
2011-07-17 1:44 ` erik quanstrom
2011-07-17 7:38 ` tlaronde
2011-07-17 8:44 ` Bakul Shah
2011-07-17 10:02 ` tlaronde
2011-07-17 12:04 ` dexen deVries
2011-07-17 15:24 ` erik quanstrom
2011-07-17 15:28 ` ron minnich
[not found] ` <CAP6exYL2DJXbKfPZ8+D5uL=fRWKEyr8vY2OVc4NTO3wsFo=Unw@mail.gmail.c>
2011-07-17 15:32 ` erik quanstrom
2011-07-17 17:16 ` Bakul Shah
2011-07-17 17:21 ` erik quanstrom
2011-07-17 15:51 ` erik quanstrom
2011-07-17 16:12 ` dexen deVries
2011-07-17 16:37 ` tlaronde [this message]
2011-07-17 10:08 ` Ethan Grammatikidis
2011-07-17 14:50 ` erik quanstrom
2011-07-17 17:01 ` Ethan Grammatikidis
2011-07-17 3:39 ` Joel C. Salomon
2011-07-17 7:01 ` tlaronde
2011-07-17 15:05 ` Joel C. Salomon
2011-07-17 15:26 ` erik quanstrom
2011-07-17 15:52 ` ComeauAt9Fans@gmail.com
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=20110717163757.GA1564@polynum.com \
--to=tlaronde@polynum.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).