From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] binutils: fix bfin compile
Date: Mon, 22 Aug 2016 00:20:24 +0200 [thread overview]
Message-ID: <20160821222023.GA10105@waldemar-brodkorb.de> (raw)
See gcc bug for details:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77311
Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
---
package/binutils/binutils.mk | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/package/binutils/binutils.mk b/package/binutils/binutils.mk
index 2936eb5..1defbb1 100644
--- a/package/binutils/binutils.mk
+++ b/package/binutils/binutils.mk
@@ -71,6 +71,12 @@ endif
BINUTILS_CONF_ENV += ac_cv_prog_MAKEINFO=missing
HOST_BINUTILS_CONF_ENV += ac_cv_prog_MAKEINFO=missing
+# gcc bug with Os/O2/O3
+# error: unable to find a register to spill in class 'CCREGS'
+ifeq ($(BR2_bfin),y)
+BINUTILS_CONF_ENV += CFLAGS="$(TARGET_CFLAGS) -O1"
+endif
+
# Install binutils after busybox to prefer full-blown utilities
ifeq ($(BR2_PACKAGE_BUSYBOX),y)
BINUTILS_DEPENDENCIES += busybox
--
2.1.4
next reply other threads:[~2016-08-21 22:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-21 22:20 Waldemar Brodkorb [this message]
2016-08-23 15:55 ` [Buildroot] [PATCH] binutils: fix bfin compile 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=20160821222023.GA10105@waldemar-brodkorb.de \
--to=wbx@openadk.org \
--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