Re: [bigloo] Beta 2.7a

[Yann Dirson <ydirson@users.sourceforge.net>]

On Thu, Jun 23, 2005 at 11:47:40AM +0200, Manuel Serrano wrote:
> > There are still problems.  The final failure looks like a bigloo issue, but I'm unsure about this warning:
> > 
> > gcc -O3  -I/build/buildd/bigloo-2.6f+2.7a-050622/build-tree/bigloo2.7a/lib/2.7a Module/java.c -c && mv java.o Module/java.o
> > /tmp/cc9CCo2w.s: Assembler messages:
> > /tmp/cc9CCo2w.s:1585: Warning: Use of 'mov' may violate WAW dependency 'GR%, % in 1 - 127' (impliedf), specific resource number is 14
> > /tmp/cc9CCo2w.s:1583: Warning: This is the location of the conflicting usage
> > 
> > make[2]: Entering directory `/build/buildd/bigloo-2.6f+2.7a-050622/build-tree/bigloo2.7a/runtime'
> > BIGLOOLIB=/build/buildd/bigloo-2.6f+2.7a-050622/build-tree/bigloo2.7a/lib/2.7a; export BIGLOOLIB; \
> > LD_LIBRARY_PATH=/build/buildd/bigloo-2.6f+2.7a-050622/build-tree/bigloo2.7a/lib/2.7a:$LD_LIBRARY_PATH; \
> >         export LD_LIBRARY_PATH; \
> >         /build/buildd/bigloo-2.6f+2.7a-050622/build-tree/bigloo2.7a/bin/bigloo  -unsafe -q -mkheap -mklib -s -no-hello -L /build/buildd/bigloo-2.6f+2.7a-050622/build-tree/bigloo2.7a/lib/2.7a Llib/make-lib.scm -heap bigloo.heap
> > 
> > File "./Ieee/symbol.scm", line 203, character 8211:
> > #       (error "getprop" "argument is neither a symbol nor a keyword" symbol)))
> > #       ^
> > # *** ERROR:getprop
> > # argument is neither a symbol nor a keyword -- long
> >     0.getprop
> > make[2]: *** [heap-c] Error 1
> > make[2]: Leaving directory `/build/buildd/bigloo-2.6f+2.7a-050622/build-tree/bigloo2.7a/runtime'
> > make[1]: *** [boot] Error 2
> > make[1]: Leaving directory `/build/buildd/bigloo-2.6f+2.7a-050622/build-tree/bigloo2.7a'
> > make: *** [stampdir/build-arch] Error 2
> This is not a Bigloo problem. This is true problem that shows that the
> system is not operational.
> 
> I don't know what to say. I have re-tested the current version on an A64
> (running a Cebian bistro) and everything is fine. may it comes from
> the FCC version. I'm using:
> 
> spe156> gcc -v
> Reading specs from /usr/lib/gcc-lib/ia64-linux/3.3.5/specs
> Configured with: ../src/configure -v --enable-languages=c,c++,java,f77,pascal,objc,ada,treelang --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-gxx-include-dir=/usr/include/c++/3.3 --enable-shared --enable-__cxa_atexit --with-system-zlib --enable-nls --without-included-gettext --with-system-libunwind --enable-clocale=gnu --enable-debug --enable-java-gc=boehm --enable-java-awt=xlib --enable-objc-gc ia64-linux
> Thread model: posix
> gcc version 3.3.5 (Debian 1:3.3.5-13)
> 
> I see that you are using gcc 3.3.1. This could be the reason...

No, that's 3.3.6 (to be precise, 1:3.3.6-7).

To the debian-ia64 team: do you know of specific problems in 3.3.6 which could explain the difference ?

-- 
Yann Dirson    <ydirson@altern.org> |
Debian-related: <dirson@debian.org> |   Support Debian GNU/Linux:
                                    |  Freedom, Power, Stability, Gratis
     http://ydirson.free.fr/        | Check <http://www.debian.org/>