Re: boot-9 compiling in guile-vm

[Neil Jerram]

2008/9/8 Andy Wingo <address@hidden>:
> Hi,
>
> I finally pushed some patches I had that enable compilation of
> boot-9.scm in guile-vm. Give it a pull. NB, you'll have to rebuild all
> your .go files -- make clean before making.

I just pulled and built: got this error...

vm-engine.c: In function 'vm_run':
vm-engine.c:199: error: unable to find a register to spill in class 'SIREG'
vm-engine.c:199: error: this is the insn:
(insn:HI 3845 3844 3846 406 vm.c:83 (parallel [
            (set (reg:SI 2 cx [1190])
                (const_int 0 [0x0]))
            (set (reg/f:SI 5 di [orig:1188 <variable>.stack_base ] [1188])
                (plus:SI (ashift:SI (reg:SI 2 cx [1190])
                        (const_int 2 [0x2]))
                    (reg/f:SI 5 di [orig:1188 <variable>.stack_base ] [1188])))
            (set (reg:SI 1 dx [1189])
                (plus:SI (ashift:SI (reg:SI 2 cx [1190])
                        (const_int 2 [0x2]))
                    (reg:SI 1 dx [1189])))
            (set (mem:BLK (reg/f:SI 5 di [orig:1188
<variable>.stack_base ] [1188]) [0 A8])
                (mem:BLK (reg:SI 1 dx [1189]) [0 A8]))
            (use (reg:SI 2 cx [1190]))
            (use (reg:SI 19 dirflag))
        ]) 704 {*rep_movsi} (insn_list:REG_DEP_TRUE 3843
(insn_list:REG_DEP_TRUE 3844 (nil)))
    (expr_list:REG_UNUSED (reg:SI 1 dx [1189])
        (expr_list:REG_UNUSED (reg/f:SI 5 di [orig:1188
<variable>.stack_base ] [1188])
            (expr_list:REG_UNUSED (reg:SI 2 cx [1190])
                (expr_list:REG_DEAD (reg:SI 19 dirflag)
                    (expr_list:REG_UNUSED (reg:SI 1 dx [1189])
                        (expr_list:REG_UNUSED (reg/f:SI 5 di
[orig:1188 <variable>.stack_base ] [1188])
                            (expr_list:REG_UNUSED (reg:SI 2 cx [1190])
                                (nil)))))))))
vm-engine.c:199: confused by earlier errors, bailing out

... which seems fantastic, because I've never seen GCC decide to dump
so much detailed bytecode information before, or to admit that it is
confused :-).  Does GCC know that we're trying to build another kind
of bytecode engine here?

Anyway, any suggestions?  I guess my GCC could be too old, but it
doesn't look it:

address@hidden:~/guile$ gcc -v
Using built-in specs.
Target: i486-linux-gnu
Configured with: ../src/configure -v
--enable-languages=c,c++,fortran,objc,obj-c++,treelang --prefix=/usr
--enable-shared --with-system-zlib --libexecdir=/usr/lib
--without-included-gettext --enable-threads=posix --enable-nls
--program-suffix=-4.1 --enable-__cxa_atexit --enable-clocale=gnu
--enable-libstdcxx-debug --enable-mpfr --with-tune=i686
--enable-checking=release i486-linux-gnu
Thread model: posix
gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)

Regards,
      Neil