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] FP register usage in Plan9 assembler
Date: Thu,  4 Feb 2016 14:04:49 +0200	[thread overview]
Message-ID: <1c082c61e95891f1a11a5ce79a04f3b7@proxima.alt.za> (raw)
In-Reply-To: <CAEAzY39TAs2yEQcZ=G-VCjgQz4HMeZLzNva8W6u1ZroyyeGoeA@mail.gmail.com>

> Plan 9 assembly is nice because it looks mostly the
> same, and the simple addressing modes are mostly consistent, but it's
> far from being really consistent between architectures.

Personally, I agree with the view that trying to generalise assemblers
across platforms is chasing a chimera.  I loved the Univac assembler I
cut my teeth on and nothing has ever given me even a hint of the
comfort I found there.  But I got used to the 8088 assembler and
managed to do some convincing work with it (I won't list the number of
issues I thought were total mindlessness by a crowd of engineers with
no visible theoretical background).

On today's platforms, assembler is not an option, it is a nightmare.
Add all the hardware trickery that belongs to microprocessors, not to
an adult computer, doesn't make anything more palatable.  Really, why
should the job of arranging memory on start up belong in the kernel
and not in a piece of dedicated logic that gets the job done and then
gets out of the way permanently, preferably switches off?

One of these day some hardware engineer will figure a way to move the
logic of the power supply into the CPU.  No, wait, we already have
voltage selections at different temperature as a kernel function, I
believe!

Bottom line?  Bless the Go Gods for having successfully subverted much
of this nonsense by providing a cross-platform development tool that
actually does what it says on the tin, despite efforts by the hardware
suppliers to relegate software development (the real thing, not
kid-scripting - or is it script-kidding?) to the smallest viable elite
of life-challenged droids.

I really do feel better now, doctor!

Lucio.




  reply	other threads:[~2016-02-04 12:04 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-01 16:47 Giacomo Tesio
2016-02-01 22:38 ` Charles Forsyth
2016-02-01 22:44   ` Charles Forsyth
2016-02-01 22:48 ` cinap_lenrek
2016-02-01 23:34   ` Giacomo Tesio
2016-02-02  0:36     ` Charles Forsyth
2016-02-02  0:58       ` Giacomo Tesio
2016-02-02 12:39         ` Aram Hăvărneanu
2016-02-02 16:42 ` Steven Stallion
2016-02-02 17:16   ` lucio
2016-02-03 15:24   ` erik quanstrom
2016-02-03 15:51     ` Steven Stallion
2016-02-03 16:36       ` erik quanstrom
2016-02-04 10:08     ` Aram Hăvărneanu
2016-02-04 12:04       ` lucio [this message]
2016-02-04 15:58         ` Ryan Gonzalez
2016-02-04 16:09           ` lucio
2016-02-04 18:06             ` Ryan Gonzalez
2016-02-04 18:14               ` balaji
2016-02-04 18:28             ` Ryan Gonzalez
2016-02-04 19:31           ` Skip Tavakkolian
2016-02-04 12:24       ` Brantley Coile
2016-02-04 12:53         ` lucio
2016-02-04 14:57           ` erik quanstrom
2016-02-04 14:05         ` Aram Hăvărneanu
2016-02-04 14:10           ` Aram Hăvărneanu
2016-02-04 14:30             ` Aram Hăvărneanu
2016-02-04 15:07         ` Charles Forsyth
2016-02-04 15:16           ` erik quanstrom
2016-02-04 15:11         ` erik quanstrom
2016-02-04 15:22           ` erik quanstrom
2016-02-04 15:26             ` Charles Forsyth
2016-02-04 20:34               ` erik quanstrom

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=1c082c61e95891f1a11a5ce79a04f3b7@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).