From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] uclibc: adapt thread implementation selection to uClibc-ng
Date: Mon, 9 Mar 2015 10:46:48 +0100 [thread overview]
Message-ID: <20150309104648.2747fd11@free-electrons.com> (raw)
In-Reply-To: <1425889628.5234.11.camel@synopsys.com>
Dear Alexey Brodkin,
On Mon, 9 Mar 2015 08:27:09 +0000, Alexey Brodkin wrote:
> We're actively working on enabling TLS/NPTL support for ARC and our
> current plan is to get it done by the next release of ARC tools -
> sometime later this spring.
>
> Even though most of things in TLS/NPTL tools for ARC work pretty well
> there're still issues to be resolved. And because this all is still in
> works we don't yet have particular branches in binutils and gcc repos I
> may recommend you to try.
>
> As for uClibc we tend to apply all changes to "arc-mainline-dev" branch
> in "https://github.com/foss-for-synopsys-dwc-arc-processors/uClibc"
> repo.
>
> Still I'd propose to wait a bit until we get something that could be
> labeled as RC and then if you're willing to start running build or
> run-time tests I'll let you know.
>
> Anyway once we enable TLS/NPTL in GNU tools for ARC I'll send patch that
> enables TLS for ARC in Buildroot - we're looking forward to having TLS
> as a default option for ARC (as most of other arches do) because of
> known benefits of TLS threading compared to Linuxthreads.
>
> So stay tuned.
Thanks Alexey for this summary of TLS support in ARC, very useful. As
you suggest, we'll wait for the next release of the ARC tools to enable
TLS by default on ARC.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-03-09 9:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-07 13:39 [Buildroot] [PATCH 0/3] uClibc-ng related fixes Thomas Petazzoni
2015-03-07 13:39 ` [Buildroot] [PATCH 1/3] uclibc: adapt thread implementation selection to uClibc-ng Thomas Petazzoni
2015-03-07 14:34 ` Yann E. MORIN
2015-03-07 16:41 ` Thomas Petazzoni
2015-03-07 17:20 ` Waldemar Brodkorb
2015-03-08 7:41 ` Thomas Petazzoni
2015-03-09 8:27 ` Alexey Brodkin
2015-03-09 9:46 ` Thomas Petazzoni [this message]
2015-03-07 17:39 ` Yann E. MORIN
2015-03-08 7:40 ` Thomas Petazzoni
2015-03-08 8:45 ` Yann E. MORIN
2015-03-08 9:13 ` Waldemar Brodkorb
2015-03-07 13:39 ` [Buildroot] [PATCH 2/3] uclibc: remove bogus comment about thread implementation selection Thomas Petazzoni
2015-03-07 14:34 ` Yann E. MORIN
2015-03-07 13:40 ` [Buildroot] [PATCH 3/3] uclibc: add patch fixing non-threaded build on Xtensa for uClibc-ng 1.0.0 Thomas Petazzoni
2015-03-07 14:40 ` Yann E. MORIN
2015-03-07 15:43 ` Waldemar Brodkorb
2015-03-07 15:50 ` Yann E. MORIN
2015-03-07 16:30 ` Thomas Petazzoni
2015-03-07 17:56 ` Waldemar Brodkorb
2015-03-08 7:35 ` Thomas Petazzoni
2015-03-07 16:29 ` Thomas Petazzoni
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=20150309104648.2747fd11@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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