Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/6] toolchain: introduce a toolchain knob for NPTL
Date: Mon, 17 Feb 2014 17:59:33 +0100	[thread overview]
Message-ID: <53023FF5.7090703@mind.be> (raw)
In-Reply-To: <20140217090354.1a2b5c73@skate>

On 17/02/14 09:03, Thomas Petazzoni wrote:
> Dear Arnout Vandecappelle,
> 
> On Mon, 17 Feb 2014 08:11:54 +0100, Arnout Vandecappelle wrote:
> 
>>  I think there is very little reason left to use NPTL on archs that
> 
> I guess you wanted to say "to *NOT* use NPTL".

 Good guess :-)

> 
>> support it, isn't there? So I would first remove the option completely
>> for these architectures. That would also make adding a comment
>> unnecessary (since it becomes an architecture feature rather than a
>> toolchain option).
> 
> While I definitely agree for the internal toolchain backend, I don't
> think this applies nicely with the external toolchain backend. We do
> not control how the external toolchains are built, and it is perfectly
> possible to build a non-NPTL toolchain on a NPTL-supported architecture
> with Crosstool-NG for example.

 Yes, but we certainly don't support all of the possible toolchains that
can be spat out by Crosstool-NG. At least, I don't think so...


> That being said, our choice could simply be to not support these cases
> at all, and check in the external toolchain backend that the toolchain
> has NPTL support if the architecture is supposed to support it.

 ... therefore I'd be in favour of this approach.

> 
> However, this kind of strategy might fail quite quickly for "growing"
> architectures. For example, ARC currently does not have NPTL support,
> but since they appear to be quite active, maybe they will implement
> NPTL support at some point. And at this moment we will have a range of
> stable, well-tested toolchains that are non-NPTL, and the possibility
> of building NPTL-capable, but not fully tested toolchains.

 But that's indeed a very good point that I didn't think of. Indeed, for
these we'll want to support both NPTL and LinuxThreads, therefore we
still need the comments.

 Taking that aspect into consideration, removing the LinuxThreads options
is not bringing any real advantage. So forget I ever mentioned it :-)


 Regards,
 Arnout

> 
> Thoughts?
> 
> Best regards,
> 
> Thomas
> 


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2014-02-17 16:59 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-13 13:22 [Buildroot] [PATCH 0/6] Add toolchain knob for NPTL Thomas Petazzoni
2014-02-13 13:22 ` [Buildroot] [PATCH 1/6] toolchain: introduce a " Thomas Petazzoni
2014-02-17  7:11   ` Arnout Vandecappelle
2014-02-17  8:03     ` Thomas Petazzoni
2014-02-17 16:59       ` Arnout Vandecappelle [this message]
2014-02-17 22:51         ` Thomas Petazzoni
2014-02-17 22:08   ` Arnout Vandecappelle
2014-02-17 22:57     ` Thomas Petazzoni
2014-02-17 23:09       ` Arnout Vandecappelle
2014-02-13 13:22 ` [Buildroot] [PATCH 2/6] docs/manual: indicate how to handle BR2_TOOLCHAIN_HAS_THREADS_NPTL Thomas Petazzoni
2014-02-13 13:46   ` Thomas De Schampheleire
2014-02-13 13:55     ` Thomas Petazzoni
2014-02-13 13:22 ` [Buildroot] [PATCH 3/6] rt-tests: use BR2_TOOLCHAIN_HAS_THREADS_NPTL Thomas Petazzoni
2014-02-13 13:22 ` [Buildroot] [PATCH 4/6] sconeserver: " Thomas Petazzoni
2014-02-13 13:22 ` [Buildroot] [PATCH 5/6] tvheadend: " Thomas Petazzoni
2014-02-13 13:22 ` [Buildroot] [PATCH 6/6] qt5: needs NPTL threads Thomas Petazzoni
2014-02-13 13:46 ` [Buildroot] [PATCH 0/6] Add toolchain knob for NPTL Mike Zick
2014-02-18 21:06   ` 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=53023FF5.7090703@mind.be \
    --to=arnout@mind.be \
    --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