From: Philipp Rumpf <prumpf@inwestnet.de>
To: parisc-linux@thepuffingroup.com
Subject: [parisc-linux] Assembly Language Changes
Date: Sun, 12 Mar 2000 15:23:53 +0100 [thread overview]
Message-ID: <20000312152353.E5281@abacus.local> (raw)
Hello,
over the last few days or so, I have been trying to get glibc to build and
work for a Linux/PA-RISC target. I came to believe it would be simpler to
change certain aspects of the assembly language used than to keep working
around them:
- Labels should always use ':'
- mnemonics in the first column should be interpreted normally.
- register names should always start with '%', not be specified by an
integer
- where pa2.0 and pa1.1 differ in opcode names aso, the pa2.0 version
should be used ("b,l" rather than "bl")
- ';' should be used rather than '!' to separate multiple statements
on the same line
- possibly there should be a line comment character to replace ';' ?
The advantages to changing the assembly dialect we use are that using cpp
to pre-process assembly instructions becomes a lot simpler (glibc makes
heavy use of this); the assembly language looks more similar to those
used for other architectures that run Linux; there is no difference
between the pa1.1 and pa2.0 versions.
The disadvantage, obviously, is that we would need to keep separate
binaries around to compile HP/UX assembly source; also, the assembly
files used by the kernel would need to be converted (and probably get
readable to more people in the process).
The actual work to implement the changes should be pretty low, and I'm
more than willing to do it (and actually already implemented the most
important (to me) changes).
Philipp Rumpf
next reply other threads:[~2000-03-12 15:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-12 14:23 Philipp Rumpf [this message]
2000-03-14 14:54 ` [parisc-linux] Assembly Language Changes Sam Creasey
2000-03-14 14:58 ` Philipp Rumpf
2000-03-15 21:16 ` Philipp Rumpf
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=20000312152353.E5281@abacus.local \
--to=prumpf@inwestnet.de \
--cc=parisc-linux@thepuffingroup.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.