All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: parisc-linux@parisc-linux.org
Subject: [parisc-linux] PARISC Userspace Updates 2003-01-14
Date: Wed, 15 Jan 2003 00:49:42 -0500	[thread overview]
Message-ID: <20030115054942.GK11375@systemhalted> (raw)

A new year and a new look at our userspace. Spurred on by Willy's email
about Kernel developments, I wanted to recap some userspace movement in
the past while: 

--- Individual Maintainers ---

- John David Anglin (JDA) is spearheading gcc development for hppa
	= Developing the coolest locking primitive ever seen in glibc.
	= Spotted nasty lock mistakes in pthreads
	= Has gcc failing less and running faster.

- Carlos O'Donell took over Glibc development from Willy
	= Sent 90% of the glibc patches upstream
	 - Big thanks to Willy who did a _lot_ of the 
	   original work, and suffered through it's maintenance.
	= Fixed rounding mask bugs in glibc fp* code
	= SHMLBA bugs squashed
	= Synchronized sigcontext between kernel and glibc.
	= Going crazy on Glibc, and writing static 64-bit Glibc.
	= We saw 2.3.x released for HPPA :)
	= Mulling over cache coherency, ldcw, and D-cache move-in's.

- I think JDA took over binutils for HPPA too...

--- Currently Being worked On ---

- GNU Glibc

	= Preparing final 10% into a form that can be accepted
	  upstream.
	= Fixing locking primitives.
	= Trying to have zero failures in 'make check'
	= fraiseexcept is still a bugger with delayed exceptions?
	= EWOULDBLOCK emulation needs analysis.
	= setjmp/longjmp implementation needs testing.
	= Implementing *context() calls.
	= Make atomic ops atomic (atomicity.h)
	= Initial implementation of a static 64-bit Glibc is in 
	  the works.

- GNU Gdb

	= Initially maintained as a patch for GDB 5.2 in debian.
	= Not an offical GDB port yet...
	= Carlos is working on and off to work this into
	  GDB 5.3, since he agreed to do it for Drow.
	= Help appreciated.
	= Thanks for various people like Richard, JDA and Randolph
	  for fixing bugs.

- GNU Binutils

	= A mystery to me... and I actively read the mailinglist :)
	= I believe we have some symbol visibility bugs.

====

Things that could be done if anyone is thinking of a project, though
help on the above is much more appreciated.

- Prelink on HPPA, requiring some binutils/glibc changes
	= http://freshmeat.net/projects/prelink/?topic_id=253
- NTPL on HPPA, requiring gcc/binutils/glibc changes
	= http://people.redhat.com/drepper/nptl-design.pdf
	= http://people.redhat.com/drepper/tls.pdf

====

How other ports do it, I'm not sure. There's a lot of love in this
particular port :) Again, many thanks to all of the hardworking
individuals who help. 

Cheers,
Carlos.

p.s. Any glaring inconsistencies or lack of knowledge are mine and mine
     alone, so feel free to correct them.

             reply	other threads:[~2003-01-15  5:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-15  5:49 Carlos O'Donell [this message]
2003-01-15  6:40 ` [parisc-linux] PARISC Userspace Updates 2003-01-14 John David Anglin
2003-01-15 12:37 ` Matthew Wilcox
2003-01-15 18:48   ` 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=20030115054942.GK11375@systemhalted \
    --to=carlos@baldric.uwo.ca \
    --cc=parisc-linux@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.