Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] protobuf: apply patch to compile for PowerPC
Date: Fri, 5 Feb 2016 14:09:09 +0100	[thread overview]
Message-ID: <20160205140909.764ff2e6@free-electrons.com> (raw)
In-Reply-To: <1851498233.1377552.1454670293384.JavaMail.zimbra@datacom.ind.br>

Hello Henrique,

On Fri, 5 Feb 2016 09:04:53 -0200 (BRST), Henrique Marks wrote:

> I agree with you, but let me say that the original patch just corrects a "syntax error" in the code !
> 
> + #define GOOGLE_PROTOBUF_ATOMICOPS_ERROR \
> +-#error "Atomic operations are not supported on your platform"
> ++"Atomic operations are not supported on your platform"

Correct. In fact I thought it was only with recent compilers, but it is
probably incorrect regardless of the gcc version, and it doesn't fail
in all cases because we ensure that protobuf is only built on
architecture on which protobuf has built-in support for atomic
operations. And therefore you don't fall into the #else cases where
this bogus error macro is used.

> This syntax error correction was submitted upstream, but wasnt
> applied to protobuf 2.6.1, just to protobuf 3x series. As we cannot
> drive the push to protobuf 3.x series right now (but we can in the
> near future, as soon as the first 3.x appears), we submitted a patch
> to buildroot.

Sure. But in this case, we prefer the patch to be a backport from
upstream, so that it is clearer when bumping that the patch can be
dropped.

And also, when a patch has been accepted by upstream, we have a higher
confidence that the patch is correct.

> Despite of this, the solution using the atomic patch you sent seems
> ok. We are using the patch we submmited for six months now,
> internally, and we try to send upstream everything, as soon as
> possible, so that we can keep up with the upstream tree. When your
> solution goes in, we can remove our internal patch (it is submmited
> in protobuf upstream 3.x anyway).

OK. Could you work on a proper patch series on the atomic series is
merged in master ?

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2016-02-05 13:09 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 [this message]
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
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=20160205140909.764ff2e6@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