From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: "FARINATI, LEANDRO" <leandro.farinati@hp.com>,
parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] 64 userspace
Date: Wed, 15 Jan 2003 14:01:54 -0500 [thread overview]
Message-ID: <20030115190154.GA20519@systemhalted> (raw)
In-Reply-To: <200301151840.h0FIeS9I018903@hiauly1.hia.nrc.ca>
> To my knowledge, there isn't one. Roughly what is required is:
>
> 1) Kernel -- design and implement 64-bit system calls.
Currently, 64-bit kernels return bogus sigcontext structures to our
32-bit userspace, they stuff the sigcontext with 64-bit registers when
it is only expecting 32-bits. It seems like sigcontext should be
expanded to have 64-bits per register for both 32 and 64 bit kernels?
This is definately an ABI breakage. Though it's funny that not many
programs are broken under 64-bit kernels, but I guess that without
*context() calls implemented for HPPA in glibc, the returned ucontext is
not used (except for that weird LISP interpreter that Krystof was
porting).
> 2) Binutils -- port hpux 64-bit tools to linux.
I thought we had a 64-bit binutils port?
> 3) Gdb -- same as binutils.
This would require some work.
> 4) GCC -- same as binutils.
hppa64-linux-gcc?
> 5) Glibc -- implement 64-bit specific parts of ABI and system calls.
This is a biggie, 64-bit SHLIBS being the large headache.
> Are you offering support from HP? It's taken a number of years to
> get to the current state of development on the 32-bit port given the
> level of volunteer effort and support from HP. What you are asking
> won't happen for months, if not years. The time to implement a 64-bit
> userspace won't be as great as for the 32-bit port, but it still a
> very significant effort.
Perhaps we will see it's emergence in the next few years :)
c.
next prev parent reply other threads:[~2003-01-15 19:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-15 18:14 [parisc-linux] 64 userspace FARINATI,LEANDRO (HP-Brazil,ex1)
2003-01-15 18:40 ` John David Anglin
2003-01-15 18:46 ` Matthew Wilcox
2003-01-15 18:54 ` Carlos O'Donell
2003-01-15 19:01 ` Carlos O'Donell [this message]
2003-01-15 19:09 ` John David Anglin
2003-01-15 19:26 ` Carlos O'Donell
2003-01-15 19:31 ` Carlos O'Donell
2003-01-15 19:49 ` John David Anglin
2003-01-15 19:17 ` John David Anglin
2003-01-15 19:27 ` Carlos O'Donell
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=20030115190154.GA20519@systemhalted \
--to=carlos@baldric.uwo.ca \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=leandro.farinati@hp.com \
--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