This is the mail archive of the
libc-ports@sources.redhat.com
mailing list for the libc-ports project.
Re: Porting glibc to Coldfire
- From: Andreas Schwab <schwab at suse dot de>
- To: richard at codesourcery dot com
- Cc: libc-ports at sourceware dot org
- Date: Wed, 13 Sep 2006 21:07:51 +0200
- Subject: Re: Porting glibc to Coldfire
- References: <87bqqmrmne.fsf@talisman.home> <jeejvhu506.fsf@sykes.suse.de> <87hd0duq69.fsf@talisman.home> <jemza48l8v.fsf@sykes.suse.de> <87lkpo2wml.fsf@talisman.home>
Richard Sandiford <richard@codesourcery.com> writes:
> Andreas Schwab <schwab@suse.de> writes:
>> How did you handle the lack of TLS support?
>
> A few local hacks to the libc/ tree, I'm afraid.
That's the main reason I haven't bothered to check in any fixes for the
m68k port yet.
> From that point of view, you could argue that there's not much point
> applying the patch. But the same problem affects the current m68k port
> too, and I hope the patch is strict improvement.
I agree. Still it would be nice if we could develop a TLS ABI for the
m68k.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."