From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] strongswan: needs atomics
Date: Wed, 8 Apr 2015 23:22:30 +0200 [thread overview]
Message-ID: <20150408232230.362b95bd@free-electrons.com> (raw)
In-Reply-To: <55259A87.7050504@zacarias.com.ar>
Dear Gustavo Zacarias,
On Wed, 08 Apr 2015 18:15:51 -0300, Gustavo Zacarias wrote:
> I'd venture to say the first (hardware has atomics) - that's what it
> means right now because:
>
> 1) We don't handle libatomic, which is the fallback if HW doesn't do it.
> This would entail adding LIBS="-latomic" for autotools packages, and
> things are magically fixed.
>
> 2) We don't copy libatomic (patches sent), so we can't do 1 just yet.
>
> So basically we should rename the whole thing.
> BR2_ARCH_HAS_ATOMICS isn't precise, we need to formulate this probably
> as BR2_ARCH_NEEDS_LIBATOMIC since AFAIK the fallback is mandatory, while
> copying it for the toolchains.
> We could have BR2_TOOLCHAIN_HAS_ATOMICS to point towards
> toolchains/architectures that don't provide atomics and a fallback.
> It also means that packages that were previously excluded can, in fact,
> be used anyway as long as libatomic is thrown to the mix.
Thanks for the summary.
How do you handle Blackfin, which uses gcc 4.3, while I believe
libatomic is a new thing in gcc 4.8, no?
Are you sure all atomic intrinsics are tied to the existence of
libatomic? It's quite hard to find some good documentation on the web
about libatomic.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-04-08 21:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 15:32 [Buildroot] [PATCH] strongswan: needs atomics Gustavo Zacarias
2015-04-08 19:22 ` Thomas Petazzoni
2015-04-08 20:19 ` Gustavo Zacarias
2015-04-08 20:40 ` Thomas Petazzoni
2015-04-08 21:15 ` Gustavo Zacarias
2015-04-08 21:22 ` Thomas Petazzoni [this message]
2015-04-08 21:25 ` Gustavo Zacarias
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=20150408232230.362b95bd@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