From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Re: [parisc-linux-cvs] linux-2.5 jejb
Date: Mon, 17 Feb 2003 16:07:20 -0500 [thread overview]
Message-ID: <20030217210720.GB14711@systemhalted> (raw)
In-Reply-To: <1045499434.1749.27.camel@mulgrave>
> > This item is on my personal todo list, but I haven't talked to anyone who has
> > suggested a solution. I'm just a lowly GNU/Libc hacker, but if you suggest
> > something I _will_ write it.
>
> In general, we should probably be relying more on the generic 32/64
> compatibility layer recently introduced. I suspect the best role model
> for all of this is sparc64, since that's habitually run as a 64 bit
> kernel with (mostly) 32 bit user space.
The sparc64 code is quite frightening, but I will look to it for a role
model.
> The HACK thing should continue to work OK as long as PA-RISC has no 64
> bit user binary support, though.
Yeah, it's OK until I attempt to write make/get/set/swap/context support
in libc :)
c.
next prev parent reply other threads:[~2003-02-17 21:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030216181021.6A8514829@dsl2.external.hp.com>
2003-02-17 15:57 ` [parisc-linux] Re: [parisc-linux-cvs] linux-2.5 jejb Carlos O'Donell
2003-02-17 16:30 ` James Bottomley
2003-02-17 21:07 ` Carlos O'Donell [this message]
[not found] <20030328054702.40ADD4829@dsl2.external.hp.com>
2003-03-28 5:50 ` James Bottomley
[not found] <20030211004917.33A12482E@dsl2.external.hp.com>
2003-02-11 0:58 ` James Bottomley
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=20030217210720.GB14711@systemhalted \
--to=carlos@baldric.uwo.ca \
--cc=James.Bottomley@steeleye.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.