All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. J. Lu" <hjl@lucon.org>
To: Ryan Bradetich <rbrad@uswest.net>
Cc: Andreas Schwab <schwab@suse.de>,
	libc-alpha@sources.redhat.com,
	parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] /lib/ld.so.1 (glibc) issues on parisc-linux 2.5 kernel??
Date: Tue, 25 Mar 2003 08:12:07 -0800	[thread overview]
Message-ID: <20030325081207.B18730@lucon.org> (raw)
In-Reply-To: <20030324184447.GA26572@uswest.net>; from rbrad@uswest.net on Mon, Mar 24, 2003 at 11:44:47AM -0700

On Mon, Mar 24, 2003 at 11:44:47AM -0700, Ryan Bradetich wrote:
> > hppa is using function descriptors, AFAIK.  So you'll have to do something
> > similar to what ia64 and ppc64 are doing.
> 
> Thanks much for the reply!  I will investigate the function descriptors and
> see if that accounts for the different in offsets.  If so, I just need to
> figure out which side needs to be fixed :)
> 

I posted a patch a long time ago to unify function descriptor handling
such that ia64 and pa-risc don't have to reinvent the wheel.


H.J.

  parent reply	other threads:[~2003-03-25 16:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-24  8:05 [parisc-linux] /lib/ld.so.1 (glibc) issues on parisc-linux 2.5 kernel?? Ryan Bradetich
2003-03-24  9:48 ` Andreas Schwab
2003-03-24  9:48 ` Andreas Schwab
2003-03-24 18:44   ` Ryan Bradetich
2003-03-24 18:44   ` Ryan Bradetich
2003-03-25 16:12     ` H. J. Lu
2003-03-25 16:12     ` H. J. Lu [this message]
2003-03-26  0:50       ` [parisc-linux] Function descriptors fall behind Sysdep-cancel, Less failures, and ABI files for Roland Carlos O'Donell
2003-03-26  0:50       ` Carlos O'Donell
  -- strict thread matches above, loose matches on Subject: below --
2003-03-24  8:05 [parisc-linux] /lib/ld.so.1 (glibc) issues on parisc-linux 2.5 kernel?? Ryan Bradetich
2003-03-21  4:18 Ryan Bradetich
2003-03-21  4:18 Ryan Bradetich

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=20030325081207.B18730@lucon.org \
    --to=hjl@lucon.org \
    --cc=libc-alpha@sources.redhat.com \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=rbrad@uswest.net \
    --cc=schwab@suse.de \
    /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.