public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: Mark Salter <msalter@redhat.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: libc-ports@sourceware.org
Subject: Re: [PATCH] am33: bring port up to date with NPTL support
Date: Tue, 21 Jan 2014 23:40:00 -0000	[thread overview]
Message-ID: <1390347651.10659.12.camel@deneb.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1401212249560.25161@digraph.polyomino.org.uk>

On Tue, 2014-01-21 at 22:53 +0000, Joseph S. Myers wrote:
> Any news on updating this patch for my review comments posted in June 
> 2012, and for all the subsequent relevant global changes in glibc for 
> which the port wasn't updated (or for which new files in the patch need 
> updating), with a view to getting it checked in so a further review of how 
> current the port is regarding global changes can be made on the basis of a 
> substantially working checked-in port?  I really don't think it makes 
> sense just to leave the port around in such a bit-rotten state; either it 
> should be fixed, or it should be removed from glibc (with of course the 
> potential to add a port to this architecture again in future if one is 
> posted that is up-to-date with current glibc).
> 

Sorry about letting this linger. At this point, I think removing it is
the thing to do. The tls bits never got to upstream gcc and I ran into
issues with the toolchain I couldn't get past.


  reply	other threads:[~2014-01-21 23:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-18 14:47 Mark Salter
2012-06-18 15:23 ` Joseph S. Myers
2012-06-18 15:41   ` Joseph S. Myers
2012-06-18 17:00   ` Joseph S. Myers
2014-01-21 22:53 ` Joseph S. Myers
2014-01-21 23:40   ` Mark Salter [this message]
2014-01-22  0:02     ` Joseph S. Myers

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=1390347651.10659.12.camel@deneb.redhat.com \
    --to=msalter@redhat.com \
    --cc=joseph@codesourcery.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).