9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Sascha Retzki" <sretzki@gmx.de>
To: 9fans@cse.psu.edu
Subject: [9fans] sparc64 port
Date: Sat, 26 Aug 2006 16:40:00 +0200	[thread overview]
Message-ID: <1e2cac07e8e7f1908cef95c5b6da0613@mail.gmx.net> (raw)


Hi friends,


I tried out Newshams sparc64 ports today (the latest tarball), and I experienced two and a half problems.

First of, there is a file missing in /sys/src/ape/lib/9/sparc64: getcallerpc.s.
As it is a oneliner which just returns 'something' ( I failed to parse it, honestly my asm is bad ), I just copied over the sparc/getcallerpc.s. (Hit me with your cluesticks later)

That again made ghostscript (and only ghostscript) not compile, syntax errors in gdevddrw.c arround an int64_t c; .. anyway. I won't use gs on sparci right now, anyway ;)


The other major problem is that the kernel does not build. I don't know how it is supposed to work, anyway. main.c modulglobally declares FPsave initfp which is used in main.c/miscinit(): savefpregs(&initfp); but also in trap.c/fpenable(): restorefpregs(&initfp);, which is called by trapinit() (which makes me think trap.c is a 'young' module which has never been tested).


Furthermore, I had to copy pc/pcf to sparc64/sparc64f, including a lot of tweaks of course - a working default-config may have been cool :P


That's how far I got. Tim, are you still here? Any comments? Anybody looked into this more deeply? Made it work?



Mfg, Sascha



             reply	other threads:[~2006-08-26 14:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-26 14:40 Sascha Retzki [this message]
2006-09-16 14:57 ` Sascha Retzki

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=1e2cac07e8e7f1908cef95c5b6da0613@mail.gmx.net \
    --to=sretzki@gmx.de \
    --cc=9fans@cse.psu.edu \
    /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).