From: Jan Heylen <heyleke@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v6 3/4] m68k_cf5208: suffers from gcc 64735
Date: Thu, 4 Jan 2018 13:28:30 +0100 [thread overview]
Message-ID: <1515068911-21112-4-git-send-email-heyleke@gmail.com> (raw)
In-Reply-To: <1515068911-21112-1-git-send-email-heyleke@gmail.com>
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>
---
toolchain/toolchain-common.in | 1 +
1 file changed, 1 insertion(+)
diff --git a/toolchain/toolchain-common.in b/toolchain/toolchain-common.in
index d743c63..0000713 100644
--- a/toolchain/toolchain-common.in
+++ b/toolchain/toolchain-common.in
@@ -22,6 +22,7 @@ config BR2_TOOLCHAIN_HAS_GCC_BUG_64735
default y if BR2_ARM_CPU_ARMV4
default y if BR2_ARM_CPU_ARMV5
default y if BR2_sparc_v8
+ default y if BR2_m68k_cf5208
depends on !BR2_TOOLCHAIN_GCC_AT_LEAST_7
config BR2_TOOLCHAIN_HAS_NATIVE_RPC
--
2.7.4
next prev parent reply other threads:[~2018-01-04 12:28 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 ` Jan Heylen [this message]
2018-01-07 22:45 ` [Buildroot] [PATCH v6 3/4] m68k_cf5208: suffers from gcc 64735 Thomas Petazzoni
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=1515068911-21112-4-git-send-email-heyleke@gmail.com \
--to=heyleke@gmail.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