Has anyone successfully bootstrapped gcc-4.6.3 on m68k?
Hello group,
This post is a bit off-topic since I am not actually trying to bootstrap gcc-4.6.3 on Debian but on another m68k system.
I have been tinkering with my NeXTstation Turbo Color for quite a while and among other things I was able to (almost) port gcc-3.2.3. At least I have the C portion working reasonably well. This was a bit of a shock, since the most "recent" gcc that anyone else was able to port was 2.95.3, and NEXTSTEP shipped with cc based on gcc-2.5.8. And I am _not_ a developer or a programmer, just a hobbyist that enjoys tinkering with classic computer systems.
With some nudging and elbow grease, I was able to almost complete stage1 of the bootstrap process on gcc-4.6.3. Unfortunately I got an ICE while compiling unwind-dw2.c:
In file included from ../../../../src/gcc-4.6.3-NS-1/libgcc/../gcc/unwind-dw2.c:35:0:
../../../../src/gcc-4.6.3-NS-1/libgcc/../gcc/unwind-pe.h: In function 'read_encoded_value_with_base':
../../../../src/gcc-4.6.3-NS-1/libgcc/../gcc/unwind-pe.h:271:1: error: unrecognizable insn:
(jump_insn 32 31 33 6 (parallel [
(set (pc)
(plus:SI (pc)
(sign_extend:SI (reg:SI 77))))
(use (label_ref 34))
]) ../../../../src/gcc-4.6.3-NS-1/libgcc/../gcc/unwind-pe.h:207 -1
(nil)
-> 34)
../../../../src/gcc-4.6.3-NS-1/libgcc/../gcc/unwind-pe.h:271:1: internal compiler error: in extract_insn, at recog.c:2109
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
And hence my question: has anyone successfully bootstrapped gcc-4.6.3 on m68k? I am trying to figure out if I am missing something in my target configuration, since it was based on gcc-3.2.3, or if this is a generic issue with gcc-4.6.3. Before I post my silly questions in the general gcc mailing list, I though that perhaps asking here might be a good idea since there are likely more m68k users here.
I also wonder whether perhaps a different gcc-4 version is a better starting point for the NeXT?
Thank you very much for your time.
Reply to: