From: David Howells <dhowells@redhat.com>
To: lethal@linux-sh.org
Cc: dhowells@redhat.com, dhorak@redhat.com, linux-sh@vger.kernel.org,
linux-arch@vger.kernel.org
Subject: Has anyone got gcc-4.7.0 to build an SH64 kernel without dying?
Date: Tue, 29 May 2012 18:23:04 +0100 [thread overview]
Message-ID: <10426.1338312184@redhat.com> (raw)
Has anyone had any success building a gcc-4.7.0 that can build SH64 binaries
without dying? I am seeing ICEs and SEGVs:
include/linux/genhd.h:214:3: internal compiler error: Segmentation fault
mm/madvise.c:285:2: internal compiler error: Segmentation fault
mm/percpu.c: In function 'pcpu_free_area':
mm/percpu.c:602:1: error: unrecognizable insn:
(insn 74 73 75 8 (set (reg:SI 279)
(abs:SI (reg:SI 280))) mm/percpu.c:575 -1
(nil))
mm/percpu.c:602:1: internal compiler error: in extract_insn, at recog.c:2123
I'm not entirely certain what target triplet I should be using. I'm currently
using sh64-linux-gnu. It does build a compiler (and it can find its
binutils). I've also tried sh64-elf, but that doesn't work either.
David
next reply other threads:[~2012-05-29 17:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-29 17:23 David Howells [this message]
2012-05-29 20:09 ` Has anyone got gcc-4.7.0 to build an SH64 kernel without dying? Oleg Endo
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=10426.1338312184@redhat.com \
--to=dhowells@redhat.com \
--cc=dhorak@redhat.com \
--cc=lethal@linux-sh.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
/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