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/1] protobuf: fix detection of __atomic_*() built-ins
Date: Wed, 10 Feb 2016 21:00:16 +0100	[thread overview]
Message-ID: <56BB96D0.4040901@mind.be> (raw)
In-Reply-To: <1455118392-3965-1-git-send-email-casantos@datacom.ind.br>

On 10-02-16 16:33, Carlos Santos wrote:
[snip]
> +#
> +# On PowerPC, the __atomic_*() built-ins for 1-byte, 2-byte and 4-byte
> +# types are available built-in. However, the __atomic_*() built-ins for
> +# 8-byte types is implemented via libatomic, so only available since gcc
> +# 4.8.
> +#
> +# In Buildroot, to simplify things, we've decided to simply 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. 
> +#
>  # host-protobuf only builds on certain architectures
>  config BR2_PACKAGE_PROTOBUF_ARCH_SUPPORTS
>  	bool
> -	default y if BR2_arm
> -	default y if BR2_i386
> -	default y if BR2_mipsel
> -	default y if BR2_x86_64

 Sorry for my confusion, but why do you remove these? It will still work with
gcc 4.7 on arm, i386, mipsel and x86_64 because it will use its custom atomic
implementation, no?


 Regards,
 Arnout

> +	default y if BR2_TOOLCHAIN_HAS_ATOMIC
>  	depends on BR2_HOSTARCH = "x86_64" || BR2_HOSTARCH = "x86"
[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

  parent reply	other threads:[~2016-02-10 20:00 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 [this message]
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
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=56BB96D0.4040901@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