From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
Cc: libc-ports@sourceware.org, aoliva@redhat.com
Subject: Re: glibc am33 and cris architectures
Date: Tue, 21 Feb 2012 17:36:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1202211732430.18259@digraph.polyomino.org.uk> (raw)
In-Reply-To: <201202211723.q1LHNckx006503@ignucius.se.axis.com>
On Tue, 21 Feb 2012, Hans-Peter Nilsson wrote:
> > From: "Joseph S. Myers" <joseph@codesourcery.com>
> > Date: Tue, 21 Feb 2012 16:21:12 +0100
>
> > The am33 and cris glibc ports won't have worked since the 2.3-2.5 era for
> > lack of NPTL/TLS support. They are currently on the deprecation list for
> > removal after glibc 2.16 is released
> > <http://sourceware.org/glibc/wiki/Deprecation>. But given how long they
> > won't have worked, I wonder if we should just remove them now.
>
> For CRIS, I'd suggest to do that.
Thanks, done.
> When doing the (e)glibc import part of the TLS support, I
> noticed how much had changed since last synch. I suggest that
> even if someone else were to do independent work, it'd be better
> to start from scratch than be distracted by the half-way-commit
> of the originally submitted code that's currently in place.
> Best to remove it; it'll just bloat any CRIS-related patches.
I suspect ABI compatibility with the old port would also be quite tricky
(and if it comes back, it may be better for it to come back with a least
symbol version of GLIBC_2.17 or whatever is the next release version at
the time, rather than attempting ABI compatibility).
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2012-02-21 17:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-21 15:21 Joseph S. Myers
2012-02-21 17:24 ` Hans-Peter Nilsson
2012-02-21 17:36 ` Joseph S. Myers [this message]
2012-03-16 4:29 ` Alexandre Oliva
2012-03-26 17:10 ` Joseph S. Myers
2012-03-27 13:34 ` Mark Salter
2012-05-21 23:30 ` Joseph S. Myers
2012-05-22 13:24 ` Mark Salter
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=Pine.LNX.4.64.1202211732430.18259@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=aoliva@redhat.com \
--cc=hans-peter.nilsson@axis.com \
--cc=libc-ports@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).