public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug linuxthreads/12300] [PATCH] RTLD_SINGLE_THREAD_P used unconditionally but only available on ports/NPTL
Date: Wed, 08 Dec 2010 19:59:00 -0000	[thread overview]
Message-ID: <bug-12300-131-5jgAl2PYBn@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12300-131@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=12300

--- Comment #3 from joseph at codesourcery dot com <joseph at codesourcery dot com> 2010-12-08 19:44:31 UTC ---
On Wed, 8 Dec 2010, rmh at gnu dot org wrote:

> http://sourceware.org/bugzilla/show_bug.cgi?id=12300
> 
> --- Comment #2 from Robert Millan <rmh at gnu dot org> 2010-12-08 17:12:46 UTC ---
> (In reply to comment #1)
> > Linuxthreads has been dead for Linux targets at least since glibc 2.5.  We 
> > really ought to remove those directories
> > 
> > sysdeps/unix/sysv/linux/arm/eabi/linuxthreads
> > sysdeps/unix/sysv/linux/arm/linuxthreads
> > sysdeps/unix/sysv/linux/hppa/linuxthreads
> > 
> > in ports to make it clear there's nothing useful there.
> 
> Hi Joseph,
> 
> Despite its name, linuxthreads is quite portable and (despite its limitations)
> is commonly used on non-Linux targets such as kFreeBSD.

The directories I suggested removing were the sysdeps/unix/sysv/linux 
ones, not the other linuxthreads directories in ports that are nominally 
applicable to non-Linux targets.  Your patch was also for a 
sysdeps/unix/sysv/linux directory.

I don't think ports should be a dumping place for dead code someone thinks 
might conceivably be useful one day; we have version control for that.  In 
my view we should remove the various dead and unmaintained code from ports 
and just leave the ports that have some chance of being useful in more or 
less their present state.

I would strongly advise those caring about the other targets to develop 
proper POSIX threads implementations for them that use whatever interfaces 
are most appropriate for each kernel (while making sure that all the 
headers included in generic glibc code present the same interface as the 
NPTL versions do, to avoid problems with generic code only working with 
NPTL) rather than relying on long-unmaintained code that does not work 
well with current libc.  You might be able to use parts of the 
Linuxthreads code or the NPTL code in such implementations; I don't know.

> I've been unable to find a repository that hosts it.  Has it been completely
> removed from sourceware.org?  This seems unfortunate.

The CVS repository (:pserver:anoncvs@sources.redhat.com:/cvs/glibc, module 
linuxthreads) still appears to exist.  It's quite possible that write 
access was blocked when the rest of the repository was converted to git, 
and linuxthreads has not been converted to git and has no maintainers.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


  parent reply	other threads:[~2010-12-08 19:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-08 17:06 [Bug linuxthreads/12300] New: " rmh at gnu dot org
2010-12-08 17:08 ` [Bug linuxthreads/12300] " joseph at codesourcery dot com
2010-12-08 17:18 ` rmh at gnu dot org
2010-12-08 19:59 ` joseph at codesourcery dot com [this message]
2010-12-08 20:12 ` rmh at gnu dot org
2010-12-09  5:31 ` joseph at codesourcery dot com
2012-02-16 14:28 ` jsm28 at gcc dot gnu.org
2014-02-06 18:25 ` jsm28 at gcc dot gnu.org
2014-06-30  6:22 ` fweimer at redhat dot com

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=bug-12300-131-5jgAl2PYBn@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).