From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] protobuf: fix detection of __atomic_*() built-ins
Date: Sat, 27 Feb 2016 22:55:17 +0100 [thread overview]
Message-ID: <56D21B45.5070500@mind.be> (raw)
In-Reply-To: <1455730981-6316-2-git-send-email-casantos@datacom.ind.br>
On 02/17/16 18:43, Carlos Santos wrote:
> - Use the recently introduced BR2_TOOLCHAIN_HAS_ATOMIC boolean.
>
> - Import an upstream patch to fix error handling when atomic operations
> are not detected. Without this patch the build fails due to a syntax
> error instead of showing the proper message.
>
> - Add a patch to configure.ac to check if libatomic is needed and force
> linking to it (we will attempt to submit this upstream).
>
> - Disable build for SPARC64 because it fails due to a missing definition
> of Atomic64.
>
> On PowerPC, the __atomic_*() built-ins for 1-byte, 2-byte and 4-byte
> types are available built-in. The corresponding built-ins for 8-byte
> types, however, are implemented via libatomic, so requiring gcc >= 4.8.
>
> In Buildroot, to simplify things, it was decided to require gcc 4.8 as
> soon as the architectures has at least one __atomic_*() built-in variant
> that requires libatomic.
>
> Since protobuf most likely only uses the 1, 2 and 4-byte variants, it
> *could* technically build with gcc 4.7. This is probably not a big deal,
> and we can live with requiring gcc 4.8 on PowerPC to build protobuf. The
> same restriction applies to SPARC.
>
> The build for SPARC64 breaks even using the master branch of protobuf
> due to undefined references to some NoBarrier_Atomic*() functions.
>
> Signed-off-by: Henrique Marks <henrique.marks@datacom.ind.br>
> Signed-off-by: Carlos Santos <casantos@datacom.ind.br>
Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
The comment in Config.in is perhaps a bit heavy, but it definitely doesn't hurt.
[snip]
--
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: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2016-02-27 21:55 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 13:08 [Buildroot] [PATCH 1/1] protobuf: apply patch to compile for PowerPC Carlos Santos
2016-02-04 23:06 ` Thomas Petazzoni
2016-02-05 11:04 ` Henrique Marks
2016-02-05 13:09 ` Thomas Petazzoni
2016-02-05 13:22 ` Henrique Marks
2016-02-05 13:37 ` Thomas Petazzoni
2016-02-07 21:19 ` Thomas Petazzoni
2016-02-10 15:25 ` Carlos Santos
2016-02-10 15:57 ` Thomas Petazzoni
2016-02-10 16:32 ` Carlos Santos
2016-02-10 16:44 ` Thomas Petazzoni
2016-02-10 16:50 ` Carlos Santos
2016-02-10 18:30 ` Carlos Santos
2016-02-10 20:13 ` Thomas Petazzoni
2016-02-11 15:14 ` Carlos Santos
2016-02-10 15:33 ` [Buildroot] [PATCH 1/1] protobuf: fix detection of __atomic_*() built-ins Carlos Santos
2016-02-10 15:50 ` Thomas Petazzoni
2016-02-10 18:42 ` Carlos Santos
2016-02-10 20:06 ` Arnout Vandecappelle
2016-02-10 20:00 ` Arnout Vandecappelle
2016-02-11 14:56 ` Carlos Santos
2016-02-11 15:23 ` Carlos Santos
2016-02-17 17:43 ` [Buildroot] [PATCH v2 0/1] " Carlos Santos
2016-02-17 17:43 ` [Buildroot] [PATCH v2 1/1] " Carlos Santos
2016-02-27 21:55 ` Arnout Vandecappelle [this message]
2016-03-20 22:43 ` Thomas Petazzoni
2016-02-17 18:33 ` [Buildroot] [PATCH v2 0/1] " Carlos Santos
2016-02-17 20:51 ` 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=56D21B45.5070500@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 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.