Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Randolph Chung <randolph@tausq.org>
To: Joel Soete <joel.soete@tiscali.be>
Cc: parisc-linux@lists.parisc-linux.org, Helge Deller <deller@gmx.de>
Subject: [parisc-linux] Re: Xfree-server and Xhp ?
Date: Sun, 13 Jul 2003 09:20:54 -0700	[thread overview]
Message-ID: <20030713162054.GF20673@tausq.org> (raw)
In-Reply-To: <3F117AA5.6090402@tiscali.be>

> Into mklinux sources I also find back <machine/asm.h> it would be easy with 
> the help of kernel documentation to 'reverse' it for parisc linux (seems to 
> be trivial).

> Does it exist some doc or tips to do this kind of obj translation 'som' -> 
> 'elf'?

well, not that i know of, but it should work almost as is. most of these
are actually differences between the HP assembler and the GNU assembler,
rather than differences between SOM and ELF.

> >      .space  $TEXT$
> >      .subspa $CODE$

change to ".text"

> >
> >      .import ngleScreenPrivIndex,data
> >
> >      .export ngleDepth8_CopyAreaFromToScreen
> >      .proc
> >      .callinfo
> >
> >ngleDepth8_CopyAreaFromToScreen
add colon (:) at end

> >      ldo 0x40(sp),sp
> >      stw arg0,-0x64(sp)
> >      stw arg1,-0x68(sp)
> >      stw arg2,-0x6c(sp)
> >      stw arg3,-0x70(sp)
> >      ldw -0x68(sp),r1
> [...]
> (arg[0..3], r[0..], t[1..4] beeing labels defined <machine/asm.h>)

shouldn't need the labels, the assembler recognizes these. but you need
to put % in front of all the register names in order for the GNU
assembler to accept the input. (ldo 0x40(%sp),%sp, etc)

HTH,
randolph
-- 
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/

  reply	other threads:[~2003-07-13 16:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-13 15:28 [parisc-linux] Xfree-server and Xhp ? Joel Soete
2003-07-13 16:20 ` Randolph Chung [this message]
2003-07-14  5:39   ` [parisc-linux] " Joel Soete
2003-07-14  5:44     ` Randolph Chung
2003-07-14  6:04       ` Joel Soete
2003-07-18 22:37         ` Joel Soete

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=20030713162054.GF20673@tausq.org \
    --to=randolph@tausq.org \
    --cc=deller@gmx.de \
    --cc=joel.soete@tiscali.be \
    --cc=parisc-linux@lists.parisc-linux.org \
    /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