From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] openpgm: Blacklist Blackfin ADI 2014R1 toolchain
Date: Sun, 8 Mar 2015 18:30:23 +0100 [thread overview]
Message-ID: <20150308183023.06960971@free-electrons.com> (raw)
In-Reply-To: <54FC7C44.1040707@openwide.fr>
Dear Romain Naour,
On Sun, 08 Mar 2015 17:43:48 +0100, Romain Naour wrote:
> > Also, at some point, we will need to really on the ARCH_HAS_ATOMICS
> > stuff for this.
> really -> rely
Right. But it's not a commit log, so do we care about typos ? :-)
> You mean BR2_ARCH_HAS_ATOMICS ?
> But it's set by default for bfin configs.
Yes. Back when we introduced BR2_ARCH_HAS_ATOMICS, but wondered whether
it should be BR2_ARCH_HAS_ATOMICS or BR2_TOOLCHAIN_HAS_ATOMICS, i.e
whether we would have the case of an architecture that does support
atomic intrinsics, but has certain toolchain versions for this
architecture that do not.
I don't remember if we carefully check whether Blackfin has atomic
intrinsics or not.
> config BR2_ARCH_HAS_ATOMICS
> # The following toolchains lack required compiler intrinsics
> depends on !BR2_TOOLCHAIN_EXTERNAL_BLACKFIN_UCLINUX_2014R1
> depends on !BR2_TOOLCHAIN_EXTERNAL_BLACKFIN_UCLINUX_2013R1
> depends on !BR2_TOOLCHAIN_EXTERNAL_BLACKFIN_UCLINUX_2012R2
> default y
Nope. We first need to find out whether the Blackfin architecture has
what's needed to provide atomic intrinsics. Depending on that, we'll
now if it's a toolchain limitation or not.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-03-08 17:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-07 18:51 [Buildroot] [PATCH] openpgm: Blacklist Blackfin ADI 2014R1 toolchain Romain Naour
2015-03-08 7:53 ` Thomas Petazzoni
2015-03-08 16:43 ` Romain Naour
2015-03-08 17:30 ` Thomas Petazzoni [this message]
2015-03-12 21:47 ` Romain Naour
2015-03-13 6:25 ` 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=20150308183023.06960971@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