bug-hurd
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: PowerPC port


From: Peter Bruin
Subject: Re: PowerPC port
Date: Fri, 12 Oct 2001 00:53:43 +0200
User-agent: Internet Messaging Program (IMP) 2.3.7-cvs

I stole much of the signal code from sysdeps/mach/hurd/alpha (is there an Alpha
port of the Hurd?). Actually, there is at least one bug in my powerpc code: in
sigreturn, all the registers are restored except for the one (CTR) which holds
the return value right before returning. I don't know if there is a way for a
thread to restore all of its registers. Also, I have never tested if
rpc_trampoline works.

I'll post my code as soon as I can, but it may take a couple of days.

Peter Bruin
pjbruin@dds.nl


Quoting Roland McGrath <roland@gnu.org>:

> > Most changes I had to make were either processor-related or had to do
> > with the differences between GNUMach and OSF Mach (which already existed
> > on the PowerPC, so that I didn't have to worry about getting Mach to
> > work).  And _I_ was amazed that I didn't have to change anything in the
> > Hurd code (except for the GNU vs.  OSF Mach things)!
> 
> We've always thought it was a clean design, thank you very much.
> 
> Aside from the kernel, the hard porting work is the signals code in libc.
> If you got this code to work right, well you're the first person to do it
> without help from me, so congratulations!  
> 
> I'd like to get your code incorporated.  I hope your ppc-specific changes
> are easy to separate from your osfmach-specific changes.  I would like to
> get the ppc hurd code into libc on its own, so it's ready to go if anybody
> ever ports gnumach (or a different microkernel) to ppc.  
> 
> Also, there has been some interest in the past in running the hurd on top
> of osfmach on x86.  If your osfmach support code is clean, it should cover
> that pretty well too.
> 
> I am very eager to see all your code.
> 



reply via email to

[Prev in Thread] Current Thread [Next in Thread]