From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v6 3/4] m68k_cf5208: suffers from gcc 64735
Date: Sun, 7 Jan 2018 23:45:29 +0100 [thread overview]
Message-ID: <20180107234529.6f31ced4@windsurf> (raw)
In-Reply-To: <1515068911-21112-4-git-send-email-heyleke@gmail.com>
Hello,
On Thu, 4 Jan 2018 13:28:30 +0100, Jan Heylen wrote:
> From: Jan Heylen <jan.heylen@nokia.com>
>
> so add it to the list of BR2_TOOLCHAIN_HAS_GCC_BUG_64735
>
> Identified experimentally by using exception_ptr with m68k_cf5208 and
> looking at the value of ATOMIC_INT_LOCK_FREE. ATOMIC_INT_LOCK_FREE = 1,
> so the issue is present. Also verified that gcc 7.x fixed it also for cf5208.
>
> Signed-off-by: Jan Heylen <jan.heylen@nokia.com>
I've applied, after slightly tweaking the commit log:
toolchain: m68k coldfire is also affected by gcc bug 64735
Verified experimentally by using exception_ptr with m68k_cf5208 and
looking at the value of ATOMIC_INT_LOCK_FREE. ATOMIC_INT_LOCK_FREE=1,
so the issue is present. Also verified that gcc 7.x fixed it also for
cf5208.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2018-01-07 22:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-04 12:28 [Buildroot] [PATCH v6 0/4] Opentracing-cpp: new package Jan Heylen
2018-01-04 12:28 ` [Buildroot] [PATCH v6 1/4] rabbitmq-c: BUILD_SHARED_LIBS is handled in pkg-cmake.mk Jan Heylen
2018-01-07 22:44 ` Thomas Petazzoni
2018-01-04 12:28 ` [Buildroot] [PATCH v6 2/4] pkg-cmake: add note on BUILD_STATIC_LIBS Jan Heylen
2018-01-07 22:45 ` Thomas Petazzoni
2018-01-04 12:28 ` [Buildroot] [PATCH v6 3/4] m68k_cf5208: suffers from gcc 64735 Jan Heylen
2018-01-07 22:45 ` Thomas Petazzoni [this message]
2018-01-08 21:53 ` Peter Korsgaard
2018-01-04 12:28 ` [Buildroot] [PATCH v6 4/4] opentracing-cpp: new package Jan Heylen
2018-01-07 22:45 ` 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=20180107234529.6f31ced4@windsurf \
--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 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.