public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Finn Thain <fthain@telegraphics.com.au>
To: Maxim Kuvyrkov <maxim@codesourcery.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Andreas Schwab <schwab@linux-m68k.org>,
	linux-m68k@vger.kernel.org
Subject: Re: Add private syscalls to support NPTL
Date: Thu, 29 Oct 2009 03:38:23 +1100 (EST)	[thread overview]
Message-ID: <alpine.OSX.2.00.0910290323070.564@silk.local> (raw)
In-Reply-To: <4AE7EAC2.8050409@codesourcery.com>



On Wed, 28 Oct 2009, Maxim Kuvyrkov wrote:

> Finn Thain wrote:
> > 
> > On Mon, 26 Oct 2009, Maxim Kuvyrkov wrote:
> > 
> > > Maxim Kuvyrkov wrote:
> > > ...
> > > > Geert, in case there'll be further changes in the NPTL patch, 
> > > > would you like me submit full patch against original tree or only 
> > > > the incremental difference?
> > > Ping.
> > > 
> > > Geert, did you have a chance to look over the patch from Oct. 2 
> > > 2009?
> > > 
> > > I've done a lot of testing since then and TLS/NPTL support on 
> > > m68k/ColdFire is now stable enough to have no unexpected failures on 
> > > binutils, gcc, g++, libstdc++ and glibc testsuites.
> > 
> > Nice work. I'm looking forward to eglibc patches so I can build a 
> > current toolchain.
> 
> We [CodeSourcery] have just updated all of our toolchains, and the 
> GNU/Linux toolchain is based on EGLIBC 2.10 and has well tested TLS/NPTL 
> support.  If you are targeting ColdFire you can simply download the 
> toolchain at <http://www.codesourcery.com/sgpp/lite/coldfire>.

At the moment I'm more interested in the m68k toolchain, particularly for 
debian. But thanks for the link, I was unaware of the free download.

> > I suppose you can't really backport to eglibc 2.10 until the siginfo 
> > question is resolved. It appears from the list traffic that the 
> > consensus is to adopt the generic struct layout here. Is that the 
> > solution that you've used in testing?
> 
> I'm not sure if any parts of the m68k kernel port depend on the custom 
> layout of siginfo, so I've only fixed the pieces which I'm sure are 
> wrong.  I.e, I've been testing with this 
> <http://marc.info/?l=linux-m68k&m=125447365311948&w=2> patch.
> 
> > If so, can you send the patches you been testing?
> 
> All the patches are in the mailing lists.
> 
> The kernel patches are at
> 
> http://marc.info/?l=linux-m68k&m=125447760017098&w=2
> http://marc.info/?l=linux-m68k&m=125447365311948&w=2
> 
> The [E]GLIBC patches are at
> 
> [M68K/ColdFire patch 1/n] Update sysdep.h
> http://sourceware.org/ml/libc-ports/2009-08/msg00006.html
> 
> [M68K/ColdFire patch 2/n] Add CFI information to dl-trampoline.S
> http://sourceware.org/ml/libc-ports/2009-08/msg00007.html
> 
> [M68K/ColdFire patch 3/n] Update jmpbuf-unwind.h
> http://sourceware.org/ml/libc-ports/2009-08/msg00008.html
> 
> [M68K/ColdFire patch 4/n] Remove kernel headers
> Update by hand to match your kernel
> 
> [M68K/ColdFire patch 5/n] Main NPTL patch
> http://sourceware.org/ml/libc-ports/2009-10/msg00006.html
> http://sourceware.org/ml/libc-ports/2009-10/msg00030.html
> 
> [M68K/ColdFire patch 6/n] Add TLS relocations to elf/elf.h
> http://sourceware.org/ml/libc-ports/2009-08/msg00012.html
> Should I post this one to glibc-alpha@ for the review?
> 
> [M68K/ColdFire patch 7/n] Handle libgcc_s.so.2
> http://sourceware.org/bugzilla/show_bug.cgi?id=4457
> 
> Let me know if you find any particular problems with these patches.
> 

That's a great help, thanks.

Finn

  reply	other threads:[~2009-10-28 16:38 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-17 21:48 Add private syscalls to support NPTL Maxim Kuvyrkov
2009-08-17 22:11 ` Andreas Schwab
2009-08-18  7:15   ` Maxim Kuvyrkov
2009-08-18  8:06     ` Andreas Schwab
2009-08-18  8:56       ` Maxim Kuvyrkov
2009-08-18  9:22         ` Geert Uytterhoeven
2009-08-18  9:36           ` Maxim Kuvyrkov
2009-08-18 18:18           ` Andreas Schwab
2009-08-23 20:21           ` Maxim Kuvyrkov
2009-08-25 19:43             ` Maxim Kuvyrkov
2009-08-28 10:51               ` Maxim Kuvyrkov
2009-10-02  9:59                 ` Maxim Kuvyrkov
2009-10-26 15:01                   ` Maxim Kuvyrkov
2009-10-28  1:19                     ` Finn Thain
2009-10-28  6:54                       ` Maxim Kuvyrkov
2009-10-28 16:38                         ` Finn Thain [this message]
2009-11-06  8:38                         ` Finn Thain
2009-11-06  8:59                           ` Maxim Kuvyrkov
2009-11-10  4:07                             ` Finn Thain
2009-11-10  4:20                               ` Brad Boyer
2009-11-10 10:51                               ` Maxim Kuvyrkov
2009-11-10 16:11                                 ` Finn Thain
2009-08-17 22:18 ` Andreas Schwab
2009-08-18  7:10   ` Maxim Kuvyrkov
2009-08-18  2:28 ` Brad Boyer
2009-08-18  7:07   ` Maxim Kuvyrkov
2009-08-18 23:40     ` Brad Boyer
2009-08-19  8:06       ` Maxim Kuvyrkov
2009-08-19  8:35       ` Andreas Schwab
2009-12-07  8:38 ` Maxim Kuvyrkov
2009-12-09 10:25   ` Klaus Kuehnhammer
2009-12-09 11:05     ` Maxim Kuvyrkov
     [not found]       ` <DBFD40BF-19FC-47DF-8A7C-B71261AFBD85@parq.net>
     [not found]         ` <4B1F9492.6030604@codesourcery.com>
2009-12-09 15:44           ` Klaus Kuehnhammer
2009-12-10  9:18             ` Maxim Kuvyrkov
2009-12-11 14:01   ` Geert Uytterhoeven
2009-12-11 16:23     ` Maxim Kuvyrkov
2009-12-17 17:53       ` Maxim Kuvyrkov

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=alpine.OSX.2.00.0910290323070.564@silk.local \
    --to=fthain@telegraphics.com.au \
    --cc=geert@linux-m68k.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=maxim@codesourcery.com \
    --cc=schwab@linux-m68k.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