From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Mark Salter <msalter@redhat.com>
Cc: libc-ports@sourceware.org, Mike Frysinger <vapier@gentoo.org>,
Andreas Schwab <schwab@linux-m68k.org>,
Richard Henderson <rth@twiddle.net>,
Carlos O'Donell <carlos@systemhalted.org>
Subject: Re: Ports state for 2.16 regarding global changes
Date: Fri, 15 Jun 2012 16:41:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1206151637030.4869@digraph.polyomino.org.uk> (raw)
In-Reply-To: <1339777097.32384.35.camel@deneb.redhat.com>
On Fri, 15 Jun 2012, Mark Salter wrote:
> On Fri, 2012-06-15 at 15:52 +0000, Joseph S. Myers wrote:
> > * am33: generally massively out of date and I have not tried to
> > identify specific changes needed.
>
> I have been working on getting this updated. ATM, I'm blocked waiting on
> a fix for a bug in the gcc patch adding am33 tls support. I expect to be
> past this sometime next week so I can actually start testing things.
>
> Would it be helpful to go ahead and post the glibc patches now or wait
> until I get them tested?
I think it makes sense to post them now. I guess you'll have a small
patch to libc - adding new relocations to elf.h - which should be sent to
libc-alpha and should be safe even during the freeze, and the rest should
be for ports. If the patches pass review then I think we should give you
write access and make you am33 maintainer so you can apply further am33
patches without prior review - given the present state of am33 support
(i.e. not substantively maintained since 2004), the changes are hardly
going to make things any worse.
(Updates to libc's README and NEWS files of course wait until the port is
actually working.)
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2012-06-15 16:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-15 15:53 Joseph S. Myers
2012-06-15 16:18 ` Mark Salter
2012-06-15 16:41 ` Joseph S. Myers [this message]
2012-06-15 17:28 ` Richard Henderson
2012-06-15 18:56 ` 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=Pine.LNX.4.64.1206151637030.4869@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=carlos@systemhalted.org \
--cc=libc-ports@sourceware.org \
--cc=msalter@redhat.com \
--cc=rth@twiddle.net \
--cc=schwab@linux-m68k.org \
--cc=vapier@gentoo.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).