RE: Raspberry Pi test results

I decided to try running ansi-test via 'make test' (rather than using the test-compiled target). It runs much faster this way. The expurgated results for ansi-test are: Test PROCLAIM.ERROR.7 failed Test SHIFTF.7 failed Test DESTRUCTURING-BIND.ERROR.10 failed Test EQUALP.5 failed Test EQUALP.6 f

RE: Raspberry Pi test results

Here are the cl-bench results for 16.1.3 release: ;; -*- lisp -*- ECL 16.1.3 ;; #| Implementation *features*: (:QUICKLISP :ASDF-PACKAGE-SYSTEM :ASDF3.1 :ASDF3 :ASDF2 :ASDF :OS-UNIX :NON-BASE-CHARS-EXIST-P :ASDF-UNICODE :WALKER :CDR-1 :

RE: Raspberry Pi test results

>> Copyright (c) 2005, Juan Jose Garcia Ripoll. > > Did you bring back an old file? If not please adjust the copyright note > accordingly. I just copied fpe_x86.c as a basis for fpe_fenv.c The code in fpe_fenv.c is copied right out of h/impl/math_fenv.h, which has a copyright date of 2010.

Raspberry Pi test results

These are the results of testing ECL on a Raspberry Pi 3B+ running Raspbian Buster. Because the Raspberry Pi 3B+ has only 1G of RAM and the default swap size for Raspbian Buster is 100M it is highly recommended that you extend the swap size to something larger. I use 1G. Instructions for doing

FP exceptions on Raspberry Pi

It appears that the VFP unit on the Raspberry Pi does not generate FPU exceptions. Therefore, no SIGFPE is generated and cannot be handled by ECL. This causes numerous 'make check' test failures. I am working on a patch. I am not very familiar with the ECL C environment so I am sure the patch wil

Build error on Raspbian Buster

When I build --with-dffi=included everything builds fine. When I build --with-dffi=system I get the following build error: (sorry for those escape sequences, not sure why they are there, I bet there is some colorization going on somewhere, which is ironic since I am blind and it doesn't help me a

Error when building ironclad

This occurs on my Raspberry Pi 3B+ running Raspbian Buster on current ECL: Script started on 2019-12-28 05:53:34-08:00 [TERM="xterm" TTY="/dev/pts/0" COLUMNS="80" LINES="24"] ]0;pi@raspberrypi: ~ pi@raspberrypi:~ $ ecl ;;; Loading "/home/pi/quicklisp/setup.lisp" ;;; Load

GC options

I have been tinkering with the various GC configuration options. I am building on Raspbian Buster (ARM), although I see the same results on an X86_64 Stretch system. The only options that seem to work are Boehm-enabled and gengc and precisegc disabled. I would like to know what *should* work. I'

RE: 16.1.3 mingw-w64-x86_64 build error

nd fix > regressions) - so I won't fix it immedietely. If nobody takes this task, > I will fix it myself before the 16.2.0 release. I've created issue for > it here: > > https://gitlab.com/embeddable-common-lisp/ecl/issues/411 > > Best regards, > > Dani

16.1.3 mingw-w64-x86_64 build error

I ran configure and only provided the --prefix argument. The 32-bit build worked fine, but the 64-bit build failed, see below. Dave cd build; make make[1]: Entering directory '/c/Dave/ecl-16.1.3/build' Building libeclmin.a... Building ecl_min.exe... ;*** Lisp core booted ECL (Embedd

ECL 16.1.3 on mingw-w64 64-bit

I am able to build ECL on mingw-w64 in 32-bit mode, but when I build in 64-bit mode it fails with a Lisp Initialization error. I notice that when building under MSVC there is an ECL_WIN64 make variable that must be set. Is there a similar variable for mingw-w64? If so, I have not found it.