From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: "H. J. Lu" <hjl@lucon.org>
Cc: libc-alpha@sources.redhat.com,
parisc-linux@lists.parisc-linux.org,
Ryan Bradetich <rbrad@uswest.net>,
Randolph Chung <tausq@debian.org>
Subject: [parisc-linux] Function descriptors fall behind Sysdep-cancel, Less failures, and ABI files for Roland.
Date: Tue, 25 Mar 2003 19:50:41 -0500 [thread overview]
Message-ID: <20030326005041.GB30578@systemhalted> (raw)
In-Reply-To: <20030325081207.B18730@lucon.org>
> 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.
Your patch is definately the correct way to go. When I initially
recommended that Ryan take the issue to the list I didn't realize it was
a function descriptor issue.
Unfortunately it falls behind the following changes:
- Sysdep-cancel support.
- Building glibc without severe testsuite failures
- Handing Roland the ABI files for HPPA.
After this I plan to follow up on the required function descriptor
changes, all along the lines of the current ia64/ppc64 implementation.
Current HPPA glibc status:
- New LinuxThreads that doesn't require explicit alignment of locks.
- 2.3.2 builds, various failures.
- Fixing sysdep-cancel support.
I should start sending the patches back here soon.
c.
next prev parent reply other threads:[~2003-03-26 0:50 UTC|newest]
Thread overview: 9+ 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 18:44 ` Ryan Bradetich
2003-03-25 16:12 ` H. J. Lu
2003-03-25 16:12 ` H. J. Lu
2003-03-26 0:50 ` Carlos O'Donell [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-24 18:44 ` [parisc-linux] /lib/ld.so.1 (glibc) issues on parisc-linux 2.5 kernel?? Ryan Bradetich
2003-03-24 9:48 ` Andreas Schwab
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=20030326005041.GB30578@systemhalted \
--to=carlos@baldric.uwo.ca \
--cc=hjl@lucon.org \
--cc=libc-alpha@sources.redhat.com \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=rbrad@uswest.net \
--cc=tausq@debian.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