From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2, 1/2] Add BR2_TOOLCHAIN_SUPPORTS_ALWAYS_LOCKFREE_ATOMIC_INTS
Date: Sat, 18 Aug 2018 21:29:53 +0200 [thread overview]
Message-ID: <20180818212953.26bf3a2f@windsurf> (raw)
In-Reply-To: <20180818174900.0ee2b668@windsurf>
Hello,
On Sat, 18 Aug 2018 17:49:00 +0200, Thomas Petazzoni wrote:
> However, we still have an issue: when static linking, libboost_atomic.a
> is produced even on platforms that do provide the "always lock-free
> atomic ints".
>
> Examples:
>
> - Cortex-M4
>
> http://autobuild.buildroot.net/results/212/212651b677cfb0763b34596d4f999103039d89bc/build-end.log
>
> $ ./host/bin/arm-linux-gcc -dM -E - < /dev/null | grep
> ATOMIC_BOOL_LOCK_FREE #define __GCC_ATOMIC_BOOL_LOCK_FREE 2
>
> - MIPS, statically linked
>
> http://autobuild.buildroot.net/results/6d3/6d3db8a67a1de75920624b3e13e8110e783ddbd9/build-end.log
>
> $ ./host/bin/mipsel-linux-gcc -dM -E - < /dev/null | grep
> ATOMIC_BOOL_LOCK_FREE #define __GCC_ATOMIC_BOOL_LOCK_FREE 2
And we have another situation here:
http://autobuild.buildroot.net/results/9c3/9c373d0b5a1a59e2271d71c480d55a90a67b84cb/build-end.log
This one is on PowerPC, and with dynamic linking. It is not going to be
solved by the BR2_TOOLCHAIN_SUPPORTS_ALWAYS_LOCKFREE_ATOMIC_INTS stuff.
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-08-18 19:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-17 22:10 [Buildroot] [PATCH v2, 1/2] Add BR2_TOOLCHAIN_SUPPORTS_ALWAYS_LOCKFREE_ATOMIC_INTS Fabrice Fontaine
2018-08-17 22:10 ` [Buildroot] [PATCH v2, 2/2] boost: thread needs atomic if GCC hasn't lock-free Fabrice Fontaine
2018-08-18 15:49 ` [Buildroot] [PATCH v2, 1/2] Add BR2_TOOLCHAIN_SUPPORTS_ALWAYS_LOCKFREE_ATOMIC_INTS Thomas Petazzoni
2018-08-18 19:29 ` Thomas Petazzoni [this message]
2018-08-18 20:09 ` Fabrice Fontaine
2018-08-18 20:20 ` 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=20180818212953.26bf3a2f@windsurf \
--to=thomas.petazzoni@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.