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 2/6] arch: mark NIOS II as affected by GCC PR libstdc++/64735
Date: Thu, 9 Feb 2017 21:32:49 +0100	[thread overview]
Message-ID: <20170209213249.6b269fe7@free-electrons.com> (raw)
In-Reply-To: <20170209174759.15819-3-joerg.krause@embedded.rocks>

Hello,

On Thu,  9 Feb 2017 18:47:55 +0100, J?rg Krause wrote:
> NIOS II does not support always lock-free atomic ints. Therefore,
> exception_ptr, nested_exception, and future from libstdc++ are not
> available before GCC 7.
> 
> Signed-off-by: J?rg Krause <joerg.krause@embedded.rocks>
> ---
>  arch/Config.in | 1 +
>  1 file changed, 1 insertion(+)

I've marked patches 2, 3 and 4 as rejected in patchwork.

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

  reply	other threads:[~2017-02-09 20:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-09 17:47 [Buildroot] [PATCH 0/6] Deal with GCC PR libstdc++/64735 Jörg Krause
2017-02-09 17:47 ` [Buildroot] [PATCH 1/6] toolchain: add option for toolchains affected by " Jörg Krause
2017-02-09 20:30   ` Thomas Petazzoni
2017-02-10  6:52     ` Jörg Krause
2017-02-09 17:47 ` [Buildroot] [PATCH 2/6] arch: mark NIOS II as " Jörg Krause
2017-02-09 20:32   ` Thomas Petazzoni [this message]
2017-02-09 17:47 ` [Buildroot] [PATCH 3/6] arch/arm: mark ARMv{4, 5} " Jörg Krause
2017-02-09 17:47 ` [Buildroot] [PATCH 4/6] arch/sparc: mark SPARCv8 " Jörg Krause
2017-02-09 17:47 ` [Buildroot] [PATCH 5/6] package/mpd: " Jörg Krause
2017-02-09 20:33   ` Thomas Petazzoni
2017-02-09 17:47 ` [Buildroot] [PATCH 6/6] package/mpd: add choice between version 0.19 and 0.20 Jörg Krause
2017-02-09 20:34   ` Thomas Petazzoni
2017-02-10  7:04     ` Jörg Krause
2017-02-11 14:25       ` Thomas Petazzoni
2017-02-10  7:34     ` Jörg Krause

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=20170209213249.6b269fe7@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