- ecl-devel - mailman3.common-lisp.net

Error when building ironclad
by Dave Richards 28 Dec '19

28 Dec '19

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: ~ [01;32mpi@raspberrypi[00m:[01;34m~ $[00m ecl ;;; Loading "/home/pi/quicklisp/setup.lisp" ;;; Loading #P"/home/pi/ecl/lib/ecl-16.1.3/asdf.fas" ECL (Embeddable Common-Lisp) 16.1.3 (git:87a1c5faed97bd0b946a4fd82f33cb666879cd4f) Copyright (C) 1984 Taiichi Yuasa and Masami Hagiya Copyright (C) 1993 Giuseppe Attardi Copyright (C) 2013 Juan J. Garcia-Ripoll Copyright (C) 2018 Daniel Kochmanski Copyright (C) 2019 Daniel Kochmanski and Marius Gerbershagen ECL is free software, and you are welcome to redistribute it under certain conditions; see file 'Copyright' for details. Type :h for Help. Top level in: #<process TOP-LEVEL 0x709fc0>. > (ql:quickload "ironclad") To load "ironclad": Load 1 ASDF system: ironclad ; Loading "ironclad" [package nibbles]................................. [package alexandria.1.0.0]........................ [package bordeaux-threads]........................ [package ironclad]................................ .................................................. .................................................. .................................................. .................................................. .................................................. .................................................. .................................................. .................................................. .................................................. ............ ;;; Internal error: ;;; ** Error code 1 when executing ;;; (SI:RUN-PROGRAM-INNER "gcc" ("-I." "-I/home/pi/ecl/include/" "-D_GNU_SOURCE" "-D_FILE_OFFSET_BITS=64" "-g" "-O2" "-fPIC" "-D_THREAD_SAFE" "-Dlinux" "-O2" "-c" ".cache/common-lisp/ecl-16.1.3-87a1c5fa-linux-armv7l/home/pi/quicklisp/dists /quicklisp/software/ironclad-v0.47/src/ciphers/kalyna.c" "-o" ".cache/common-lisp/ecl-16.1.3-87a1c5fa-linux-armv7l/home/pi/quicklisp/dists /quicklisp/software/ironclad-v0.47/src/ciphers/kalyna.o") NIL): ;;; .cache/common-lisp/ecl-16.1.3-87a1c5fa-linux-armv7l/home/pi/quicklisp/dists/ quicklisp/software/ironclad-v0.47/src/ciphers/kalyna.c: In function 'L49kalyna512_decrypt_block': ;;; .cache/common-lisp/ecl-16.1.3-87a1c5fa-linux-armv7l/home/pi/quicklisp/dists/ quicklisp/software/ironclad-v0.47/src/ciphers/kalyna.c:231231:18: note: variable tracking size limit exceeded with -fvar-tracking-assignments, retrying without ;;; static cl_object L49kalyna512_decrypt_block(cl_object v1context, cl_object v2ciphertext, cl_object v3ciphertext_start, cl_object v4plaintext, cl_object v5plaintext_start) ;;; ^~~~~~~~~~~~~~~~~~~~~~~~~~ ;;; .cache/common-lisp/ecl-16.1.3-87a1c5fa-linux-armv7l/home/pi/quicklisp/dists/ quicklisp/software/ironclad-v0.47/src/ciphers/kalyna.c: In function 'L48kalyna512_encrypt_block': ;;; .cache/common-lisp/ecl-16.1.3-87a1c5fa-linux-armv7l/home/pi/quicklisp/dists/ quicklisp/software/ironclad-v0.47/src/ciphers/kalyna.c:185126:18: note: variable tracking size limit exceeded with -fvar-tracking-assignments, retrying without ;;; static cl_object L48kalyna512_encrypt_block(cl_object v1context, cl_object v2plaintext, cl_object v3plaintext_start, cl_object v4ciphertext, cl_object v5ciphertext_start) ;;; ^~~~~~~~~~~~~~~~~~~~~~~~~~ ;;; gcc: fatal error: Killed signal terminated program cc1 ;;; compilation terminated. Condition of type: COMPILE-FILE-ERROR COMPILE-FILE-ERROR while compiling #<ironclad-source-file "ironclad" "src" "ciphers" "kalyna"> Available restarts: 1. (RETRY) Retry compiling #<ironclad-source-file "ironclad" "src" "ciphers" "kalyna">. 2. (ACCEPT) Continue, treating compiling #<ironclad-source-file "ironclad" "src" "ciphers" "kalyna"> as having been successful. 3. (RETRY) Retry ASDF operation. 4. (CLEAR-CONFIGURATION-AND-RETRY) Retry ASDF operation after resetting the configuration. 5. (ABORT) Give up on "ironclad" 6. (RESTART-TOPLEVEL) Go back to Top-Level REPL. Broken at ASDF/ACTION:PERFORM. In: #<pr

2 1

[CfP] ELS 2020, 13th European Lisp Symposium, April 27-28, Zurich
by Didier Verna 06 Dec '19

06 Dec '19

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 13th European Lisp Symposium Special Focus on Compilers Call for papers April 27 - April 28, 2020 GZ Riesbach Zürich, Switzerland http://www.european-lisp-symposium.org/2020 Sponsored by EPITA, Igalia S.L. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Invited Speakers ~~~~~~~~~~~~~~~~ Andrew W. Keep (Cisco Systems, Inc.), on the Nanopass Framework. Daniel Kochmański (Turtleware), on ECL, the Embeddable Common Lisp. Important Dates ~~~~~~~~~~~~~~~ - Submission deadline: February 13, 2020 - Author notification: March 16, 2020 - Final papers due: April 6, 2020 - Symposium: April 27 - 28, 2020 Scope ~~~~~ The purpose of the European Lisp Symposium is to provide a forum for the discussion and dissemination of all aspects of design, implementation and application of any of the Lisp dialects, including Common Lisp, Scheme, Emacs Lisp, Clojure, Racket, ACL2, AutoLisp, ISLISP, Dylan, ECMAScript, SKILL and so on. We encourage everyone interested in Lisp to participate. The European Lisp Symposium 2020 invites high quality papers about novel research results, insights and lessons learned from practical applications, and educational perspectives. We also encourage submissions about known ideas as long as they are presented in a new setting and/or in a highly elegant way. This year's focus will be directed towards "Compilers". We especially invite submissions in the following areas: - Compiler techniques - Compiler passes - Compiler compilers - Showcasing of industrial or experimental compilers - Code generation - Compiler verification - Compiler optimizations - JIT compilers Contributions are also welcome in other areas, including but not limited to: - Context-, aspect-, domain-oriented and generative programming - Macro-, reflective-, meta- and/or rule-based development approaches - Language design and implementation - Language integration, inter-operation and deployment - Development methodologies, support and environments - Educational approaches and perspectives - Experience reports and case studies Technical Program ~~~~~~~~~~~~~~~~~ We invite submissions in the following forms: * Papers: Technical papers of up to 15 pages that describe original results or explain known ideas in new and elegant ways. * Demonstrations: Abstracts of up to 4 pages for demonstrations of tools, libraries, and applications. * Tutorials: Abstracts of up to 4 pages for in-depth presentations about topics of special interest for at least 90 minutes and up to 180 minutes. All submissions should be formatted following the ACM SIGS guidelines and include ACM Computing Classification System 2012 concepts and terms. Submissions should be uploaded to Easy Chair, at the following http://www.easychair.org/conferences/?conf=els2020 Note: to help us with the review process please indicate the type of submission by entering either "paper", "demo", or "tutorial" in the Keywords field. Programme Chair ~~~~~~~~~~~~~~~ Ioanna M. Dimitriou H. - Igalia, Spain/Germany Local Chair ~~~~~~~~~~~ Nicolas Hafner - Shinmera, Switzerland Programme Committee ~~~~~~~~~~~~~~~~~~~ Andy Wingo - Igalia, Spain/France Asumu Takikawa - Igalia, Spain/USA Charlotte Herzeel - IMEC, Intel Exascience Lab, Belgium Christophe Rhodes - Google, UK Iréne Durand - Université Bordeaux 1, France Jim Newton - EPITA Research Lab, France Kent Pitman - HyperMeta, USA Leonie Dreschler-Fischer - University of Hamburg, Germany Marco Heisig - FAU Erlangen-Nürnberg, Germany Mark Evenson - not.org, Austria Max Rottenkolber - Interstellar Ventures, Germany Paulo Matos - Igalia, Spain/Germany Robert Goldman - SIFT, USA Robert Strandh - Université Bordeaux 1, France (more PC members to be announced) -- Resistance is futile. You will be jazzimilated. Lisp, Jazz, Aïkido: http://www.didierverna.info

1 0

GC options
by Dave Richards 10 Nov '19

10 Nov '19

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'd like to generate code targeted to an embedded platform. Thanks, Dave

1 0

Script to build ECL for iOS using XCode 10 tools?
by PR 06 Oct '19

06 Oct '19

Hi, I've been searching for a more recent version of this script: https://github.com/cbbaker/ecl-iphone-builder/blob/master/build.sh but without success. Does anyone reading this have a version sitting around which would work with current Xcode 10, that is: compile ECL for iOS using the clang compiler and targeting the arm64 architecture? Thanks, Paul P.S. The premium could be a port of the 'CL REPL' app from android to the iPhone, if I get it to work, sometime in the near future.

3 10

[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

What is the best version of ECL to use right now?
by Dennis Ogbe 10 Jun '19

10 Jun '19

Hello, I am working on embedding ECL in a reasonably-sized C++ program and I have been using v16.1.3 until now, since it seems like this is the latest official release. However, it seems like there is a lot of activity and bug fixes in the develop branch and I already ran into a few bugs (for example [1]) that are fixed in develop, but are not in any release. The documentation also seems to overlap more with the develop branch than the latest release. In your opinion, what is the best and most stable ECL version to use as of June 2019? I have some reservations about simply picking a random commit from a dev branch, so I wanted to reach out and ask y'all directly. Thanks for all the hard work, this project is great! [1] https://gitlab.com/embeddable-common-lisp/ecl/issues/418

2 6