ecl-devel July 2019

ecl-devel@common-lisp.net

5 participants
6 discussions

Is this thing on? Cross-compiling for ARM
by Erik Winkels 26 Sep '20

26 Sep '20

Hi all, Not sure if this is still the place to be for ECL questions but here it goes: I'm having issues cross-compiling ECL for ARM and since this is actually the first time I'm cross-compiling stuff ever I'm kinda stuck. I want to cross-compile for ARM, *but* it is not for Android it is for Sailfish OS. There's an (unofficial) ECL package available for it but I cannot find a way to contact the author and also don't want to depend on it. On my Void Linux machine I've installed `cross-arm-linux-gnueabi` and can do a `./configure --host=arm-linux-gnueabi` but when I do `make` I get the following errors: ``` dpp: /home/brainrot/projects/eclrepl/3rd-party/ecl-git/src/c/list.d -> list.o.c Unknown symbol: mp::compare-and-swap-car Unknown symbol: mp::atomic-incf-car Unknown symbol: mp::compare-and-swap-cdr Unknown symbol: mp::atomic-incf-cdr /home/brainrot/projects/eclrepl/3rd-party/ecl-git/src/c/list.d: In function 'mp_compare_and_swap_car': /home/brainrot/projects/eclrepl/3rd-party/ecl-git/src/c/list.d:670:26: error: 'unknown' undeclared (first use in this function) return ecl_compare_and_swap(&ECL_CONS_CAR(x), old, new); ^~~~~~~ /home/brainrot/projects/eclrepl/3rd-party/ecl-git/src/c/list.d:670:26: note: each undeclared identifier is reported only once for each function it appears in /home/brainrot/projects/eclrepl/3rd-party/ecl-git/src/c/list.d: In function 'mp_atomic_incf_car': /home/brainrot/projects/eclrepl/3rd-party/ecl-git/src/c/list.d:678:26: error: 'unknown' undeclared (first use in this function) return ecl_atomic_incf(&ECL_CONS_CAR(x), increment); ^~~~~~~ /home/brainrot/projects/eclrepl/3rd-party/ecl-git/src/c/list.d: In function 'mp_compare_and_swap_cdr': /home/brainrot/projects/eclrepl/3rd-party/ecl-git/src/c/list.d:686:26: error: 'unknown' undeclared (first use in this function) return ecl_compare_and_swap(&ECL_CONS_CDR(x), old, new); ^~~~~~~ /home/brainrot/projects/eclrepl/3rd-party/ecl-git/src/c/list.d: In function 'mp_atomic_incf_cdr': /home/brainrot/projects/eclrepl/3rd-party/ecl-git/src/c/list.d:694:26: error: 'unknown' undeclared (first use in this function) return ecl_atomic_incf(&ECL_CONS_CDR(x), increment); ^~~~~~~ make[2]: *** [Makefile:88: list.o] Error 1 make[2]: Leaving directory '/home/brainrot/projects/eclrepl/3rd-party/ecl-git/build/c' make[1]: *** [Makefile:144: libeclmin.a] Error 2 make[1]: Leaving directory '/home/brainrot/projects/eclrepl/3rd-party/ecl-git/build' make: *** [Makefile:72: all] Error 2 ``` I get the feeling I'm forgetting some necessary steps. Thanks, Erik

4 19

[PATCH] Improved error detection and reporting in RESTART-BIND
by Spiros Bousbouras 20 Jul '19

20 Jul '19

If you do (restart-bind ((locutus (function cdr) :report-function "23")) (error "This is an error")) you get Excessive debugger depth! Probable infinite recursion! Quitting process: #<process TOP-LEVEL>. and ECL exits. This isn't very useful. One can find various similar examples. After the patch one would get { Condition of type: SIMPLE-ERROR Macro RESTART-BIND : "23" is not a function object Available restarts: 1. (RESTART-TOPLEVEL) Go back to Top-Level REPL. Broken at SI:BYTECODES. [Evaluation of: (RESTART-BIND ((LOCUTUS #'CDR :REPORT-FUNCTION "23")) (ERROR "This is an error"))] In: #<process TOP-LEVEL>. } which is better. The new RESTART-BIND does improved error detection and reporting in other situations too. The patch follows below. You go to directory ecl-16.1.3/src/clos/ and , assuming you have saved the patch with the filename patch , you do patch -F 0 --verbose --posix conditions.lsp patch .This assumes GNU patch , otherwise skip the --verbose --posix part. I didn't make an entry in ecl-16.1.3/CHANGELOG because I'm not sure what the required format is. The file indicates near the top that it is for version 16.1.3 .So where should one mention changes which might appear in a newer version ? @===================================================================================== *** conditions.lsp Fri Jul 19 19:37:53 2019 --- conditions.lsp.new Fri Jul 19 19:39:05 2019 *************** *** 99,118 **** for n in (if (atom names) (list names) names) for f = (simple-handler-function tag i) collect (cons n f)) *handler-clusters*))) ! (defmacro restart-bind (bindings &body forms) ! `(let ((*restart-clusters* ! (cons (list ,@(mapcar #'(lambda (binding) ! `(make-restart ! :NAME ',(car binding) ! :FUNCTION ,(cadr binding) ! ,@(cddr binding))) ! bindings)) ! *restart-clusters*))) ! ,@forms)) (defun find-restart (name &optional condition) (dolist (restart (compute-restarts condition)) (when (or (eq restart name) (eq (restart-name restart) name)) (return-from find-restart restart)))) --- 99,159 ---- for n in (if (atom names) (list names) names) for f = (simple-handler-function tag i) collect (cons n f)) *handler-clusters*))) ! (defun restart-bind-check-binding ! (name foo &rest rest ! &aux int-foo rep-foo test-foo ! (err-mes (format nil "Macro ~S :" 'restart-bind))) ! (unless (symbolp name) (error "~a ~s is not a symbol" err-mes name)) ! (unless (functionp foo) (error "~a ~s is not a function object" err-mes foo)) ! (do ((br rest (cddr br))) ! ((eq br nil) (make-restart :name name :function foo ! :report-function rep-foo ! :interactive-function int-foo ! :test-function (if test-foo test-foo ! (constantly t)))) ! (let ((key (first br)) (obj (second br))) ! (unless (functionp obj) ! (error "~a ~s is not a function object" err-mes obj)) ! (cond ((eq key :interactive-function) ! (when int-foo ! (error "~a ~s given more than once" ! err-mes :interactive-function)) ! (setq int-foo obj)) ! ((eq key :report-function) ! (when rep-foo ! (error "~a ~s given more than once" ! err-mes :report-function)) ! (setq rep-foo obj)) ! ((eq key :test-function) ! (when test-foo ! (error "~a ~s given more than once" ! err-mes :test-function)) ! (setq test-foo obj)) ! (t (error "~a Inappropriate keyword ~s" err-mes key)))))) ! ! (defmacro restart-bind (bindings &body forms ! &aux (new (list 'list)) (tail new) fb eta ! (err-mes (format nil "Macro ~S :" 'restart-bind))) ! (dolist (b bindings) ! (unless (listp b) (error "~a ~s is not a list" err-mes b)) ! (setq fb (first b)) ! (unless (symbolp fb) (error "~a ~s is not a symbol" err-mes fb)) ! (unless (second b) (error "~a ~s does not have a function argument" ! err-mes b)) ! (setq eta (list 'restart-bind-check-binding `(quote ,fb) (second b))) ! (do ((l (cddr b) (cdr l)) ! (t2 (cddr eta) (cdr t2))) ! ((eql nil l)) ! (rplacd t2 (list (first l)))) ! (rplacd tail (list eta)) ! (setq tail (cdr tail))) ! `(let ((*restart-clusters* (cons ,new *restart-clusters*))) ! ,@forms)) ! (defun find-restart (name &optional condition) (dolist (restart (compute-restarts condition)) (when (or (eq restart name) (eq (restart-name restart) name)) (return-from find-restart restart))))

2 3

Compilation failure on cygwin
by Иван Трусков 17 Jul '19

17 Jul '19

Hello I am trying to build and use ECL on windows machine under cygwin environment However, evter it is built, there arises a problem when i try to compile any lisp files, for example when running examples/build/readme.lisp Inspecting with gsb gives the picture of stack overflow on handling some exception across threads, overflow occuring in the bad case of circular calls to acquiring thread-local data (pthreads_getspecific) and processing error message from failure of it. is there recommended configuration for cygwin that would allow to overcome that kind of problem? Alternatively, what data exactly are needed for a full bug report? I would gladly provide everything relevant

3 4

Evaluating with a lexical environment
by Spiros Bousbouras 13 Jul '19

13 Jul '19

clisp provides a facility to evaluate a form in a non null lexical environment. It works as follows > (let ((a 1) (b 2)) (ext:eval-env '(format t "a is ~A b is ~A~%" a b) (ext:the-environment))) a is 1 b is 2 NIL The clisp documentation gives Macro EXT:THE-ENVIRONMENT. As in Scheme, the macro (EXT:THE-ENVIRONMENT) returns the current lexical environment. This works only in interpreted code and is not compilable! Function (EXT:EVAL-ENV form &OPTIONAL environment). evaluates a form in a given lexical environment, just as if the form had been a part of the program that the environment came from. I was wondering if ECL has something analogous or could be added easily. Looking in the ECL source I saw a si::eval-with-env function in file ecl-16.1.3/src/c/compiler.d .If you do > (find-symbol "EVAL-WITH-ENV" "SYSTEM") SI:EVAL-WITH-ENV :EXTERNAL which suggests that the function is not just for internal use. But scanning the documentation , I didn't see it mentioned. I tried (defmacro env-eval (form &environment env) `(ext:eval-with-env ,form (quote ,env))) ENV-EVAL > (let ((v 12)) (env-eval '(print v))) The variable V is unbound. Broken at EVAL.No restarts available. Broken at EVAL. So is there a way to achieve this ?

2 2

Infinite loop or blocking operation in main ECL thread - what to do?
by Не Скажу 08 Jul '19

08 Jul '19

Some portion of program is scriptable with ECL, which runs in its own separate thread. What I fear, however, is that users might do something stupid and enter an infinite loop or break into debugger wondering why does the scriptable part no longer responds. For the latter breaking into debugger is disabled by default with an option to reenable it, but nevertheless knowing Murphy's law I expect the worst to happen. I would like to keep the program responsive no matter what. I was hoping I could restart ECL in such cases, so I tried terminating ECL thread first but it results in a crash. And apparently after calling cl_shutdown ECL shuts down for good and a second call to cl_boot does not work so restarting does not appear as an option anyway. Is there anything I can do to keep the program running or just trust the user to do the right thing?

2 1

DEFSTRUCT non bug
by Spiros Bousbouras 01 Jul '19

01 Jul '19

This is regarding https://gitlab.com/embeddable-common-lisp/ecl/issues/469 .I don't think that the behaviour mentioned in there is a bug. (defstruct foo a b c) is top level inside file /tmp/foo.lisp and CLHS says If a defstruct form appears as a top level form, the compiler must make the structure type name recognized as a valid type name in subsequent declarations (as for deftype) and make the structure slot readers known to setf. So after (compile-file "/tmp/foo.lisp") it makes sense that FIND-CLASS would know about foo . SBCL behaves the same way.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

ecl-devel July 2019