RE: [Axiom-developer] Possible gcl bug with axiom--windows--1

[Vanuxem Grégory]

Hi Mike.

> -----Message d'origine-----
> De : Mike Thomas [mailto:address@hidden
> Envoyé : mercredi 25 mai 2005 23:48
> À : Vanuxem Grégory; Axiom-Developer
> Objet : RE: [Axiom-developer] Possible gcl bug with axiom--windows--1
>
>
> Hi Greg.
>
> Thanks for the bug report.
>
> The Windows binary relase of GCL 2.6.6  works correctly on that
> file with a
> PIV 512 Megabyte XP machine.
>
> I've got my Axiom source tree set up to test gcl 2.6.7 at the moment and I
> won't go further with your bug until that job is finished.
>
> What version of gcc are you using? Likewise what is your CPU and memory?

gcc.exe (GCC) 3.4.2 (mingw-special)
Copyright (C) 2004 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE

MinGW-RC probably 2 (2005-02-03-*)
binutils-2.15.94-20050118-1

I have used 'gcc -march=k8' without -m64.

Windows XP (R) 32bits
CPU: AMD 3000+
RAM: 1GB

Cheers,

Greg

PS: If somebody with a more classic build configuration can reproduct
this...

>
> Cheers
>
> Mike Thomas.
>
> >(compile-file "c:/junk/mflop.lisp")
>
> Compiling c:/junk/mflop.lisp.
> Warning: The OPTIMIZE quality DEBUG is unknown.
> Warning: The OPTIMIZE quality DEBUG is unknown.
> End of Pass 1.
> End of Pass 2.
> OPTIMIZE levels: Safety=0 (No runtime error checking), Space=0, Speed=3
> Finished compiling c:/junk/mflop.lisp.
> #p"c:/junk/mflop.o"
>
> >(load "c:/junk/mflop.o")
>
> Loading c:/junk/mflop.o
> DDOT-long: 190.38 MFLOPS
> DDOT-short: 510.09 MFLOPS
> DAXPY-long: 10.84 MFLOPS
> DAXPY-short: 12.76 MFLOPS
> start address -T 10254878 Finished loading c:/junk/mflop.o
> 1712
>
>
>
>