Skip to contentSkip to conversation

Has anyone got gcc-4.7.0 to build an SH64 kernel without dying?

DISCUSSION David Howells 3 participants 5 messages May 29, 2012 – May 31, 2012

Subsystems (2)
lore
Share & tools
lore
#0 lore 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

#1 lore raw
Quoted 12 lines · David Howells

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

Hmm .. abs:SI ... I'm afraid that was me. Sorry about that! Somebody noticed the problem with abs:SI on SH64 a while ago, too. However, I don't remember whether the fix made it into 4.7.0 or into the 4.7.1 branch. Could you try with the 4.7.1 branch?

Cheers,
Oleg

#2 lore raw
In reply to David Howells
Quoted 4 lines · Oleg Endo

Hmm .. abs:SI ... I'm afraid that was me. Sorry about that! Somebody noticed the problem with abs:SI on SH64 a while ago, too. However, I don't remember whether the fix made it into 4.7.0 or into the 4.7.1 branch. Could you try with the 4.7.1 branch?

There were 3 patches for sh64-elf gcc build failure on trunk:

http://gcc.gnu.org/ml/gcc-patches/2012-03/msg00208.html
http://gcc.gnu.org/ml/gcc-patches/2012-03/msg00209.html
http://gcc.gnu.org/ml/gcc-patches/2012-03/msg00210.html

which are generic for sh64 targets. The 3rd one is for the abs:SI issue. I thought that they are included in 4.7 but they aren't because they were applied just after branching 4.8 done unfortunately. I guess that these patches should be backported to 4.7.1 branch.

Regards,
kaz

#4 lore raw
In reply to David Howells
Quoted 8 lines · Kaz Kojima
Quoted 4 lines · Oleg Endo

Hmm .. abs:SI ... I'm afraid that was me. Sorry about that! Somebody noticed the problem with abs:SI on SH64 a while ago, too. However, I don't remember whether the fix made it into 4.7.0 or into the 4.7.1 branch. Could you try with the 4.7.1 branch?

There were 3 patches for sh64-elf gcc build failure on trunk:

Quoted 8 lines

http://gcc.gnu.org/ml/gcc-patches/2012-03/msg00208.html
http://gcc.gnu.org/ml/gcc-patches/2012-03/msg00209.html
http://gcc.gnu.org/ml/gcc-patches/2012-03/msg00210.html

which are generic for sh64 targets. The 3rd one is for the abs:SI issue. I thought that they are included in 4.7 but they aren't because they were applied just after branching 4.8 done unfortunately. I guess that these patches should be backported to 4.7.1 branch.

Done :)

Cheers,
Oleg