Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Philipp Rumpf <prumpf@inwestnet.de>
To: Sam Creasey <sammy@sammy.net>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Assembly Language Changes
Date: Tue, 14 Mar 2000 15:58:18 +0100	[thread overview]
Message-ID: <20000314155818.Q5281@abacus.local> (raw)
In-Reply-To: <Pine.LNX.4.21.0003140951150.1905-100000@sammyville.sammy.net>; from sammy@sammy.net on Tue, Mar 14, 2000 at 09:54:43AM -0500

> > 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:
> 
> At least in the ELF toolchain (which, I think we did change the kernel
> over to, didn't we?)  I've already begun freely banging the assembler
> syntax into a more gas-like format...   

nod.  I've got binutils, gcc, glibc, linux moved to the new assembly language
here, just waiting for everyone to have a chance to comment before committing.

> > 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).
> 
> Hmph...  I'm not sure how many people working on the port hold a deep
> value in the ability to recompile HP/UX apps (or, in this case,
> reassemble).  Just run the damn HP assembler if you feel a deep need to
> run HP programs under the linux kernel (imho).

it's a 10-line perl script to convert, so I tend to agree with dropping the
HP syntax completely.

	Philipp

  reply	other threads:[~2000-03-14 15:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-12 14:23 [parisc-linux] Assembly Language Changes Philipp Rumpf
2000-03-14 14:54 ` Sam Creasey
2000-03-14 14:58   ` Philipp Rumpf [this message]
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=20000314155818.Q5281@abacus.local \
    --to=prumpf@inwestnet.de \
    --cc=parisc-linux@thepuffingroup.com \
    --cc=sammy@sammy.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