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

[Vanuxem Grégory]

Hi,

With saved_gcl (gcl-2.6.5w) from axiom--windows--1 (downloaded two weeks
ago):


c:\MinGW\msys\home\greg\axiom--windows--1\lsp\gcl-2.6.5w\unixport\saved_gcl.
exe
>(compile-file "Bureau/mfop.lisp")

Compiling Bureau/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 Bureau/mflop.lisp.
#p"Bureau/mflop.o"

>(load "Bureau/mflop.o")

Loading Bureau/mflop.o
DDOT-long: 326.20 MFLOPS
DDOT-short: 530.24 MFLOPS

Error: Caught fatal error [memory may be damaged]
Fast links are on: do (si::use-fast-links nil) for debugging
Error signalled by LOAD.
Broken at MFLOP-TEST.  Type :H for Help.
>>(quit)

c:\MinGW\msys\home\greg\axiom--windows--1\lsp\gcl-2.6.5w\unixport\saved_gcl.
exe
>(load "Bureau/mflop.lisp")

Loading Bureau/mflop.lisp
DDOT-long: 0.93 MFLOPS
DDOT-short: 0.90 MFLOPS
DAXPY-long: 0.28 MFLOPS
DAXPY-short: 0.27 MFLOPS
Finished loading Bureau/mflop.lisp
T


The same works on linux.
I'm not sure if it's bug since first I use a
realease candidate MinGW and second gcl from axiom--linux is compiled
on AMD64 (64 bits arch).


Cheers,

Greg



PS : Original gcl-devel mailing message
(mflop.lisp from Nicolas Neuss (address@hidden)):
http://lists.gnu.org/archive/html/gcl-devel/2004-07/msg00080.html

mflop.lisp
Description: Binary data