July 2011 - armedbear-ticket - mailman3.common-lisp.net

[armedbear-ticket] [armedbear] #135: ql:FEB2011:bordeaux-threads BORDEAUX-THREADS does not work
by armedbear 07 Sep '11

07 Sep '11

#135: ql:FEB2011:bordeaux-threads BORDEAUX-THREADS does not work ------------------------------------------------+--------------------------- Reporter: mevenson | Owner: mevenson Type: defect | Status: new Priority: major | Milestone: 0.25 Component: libraries | Version: 0.24 Keywords: bordeaux-threads quicklisp threads | ------------------------------------------------+--------------------------- [http://common-lisp.net/project/bordeaux-threads/ bordeaux-threads] fails with ABCL due to a number of reasons for which I am in progress of working through patches. This issue will track the status of these patches against the progress of those patches against both [http://common- lisp.net/gitweb?p=projects/bordeaux-threads/bordeaux-threads.git;a=summary BORDEAUX-THREADS in git] and [http://www.quicklisp.org/beta/ the version distributed with QuickLisp] (the version of FEB2011 as of this writing). -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/135> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 12

[armedbear-ticket] [armedbear] #124: Failure to be an SBCL build host
by armedbear 25 Aug '11

25 Aug '11

#124: Failure to be an SBCL build host ------------------------+--------------------------------------------------- Reporter: ehuelsmann | Owner: nobody Type: defect | Status: new Priority: major | Milestone: Component: libraries | Version: Keywords: | ------------------------+--------------------------------------------------- When building SBCL with ABCL, I'm getting the error #<XP:XP-STRUCTURE ...> isn't of type STREAM Failing to continue the SBCL build. The issue here is that our pretty printer structure - which wraps a stream - isn't itself a stream. Somehow, the pretty printer stream wrapper is passed into ABCL internals expecting a STREAM, though. -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/124> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 12

[armedbear-ticket] [armedbear] #116: Installing cl-unicode via quicklisp fails
by armedbear 19 Aug '11

19 Aug '11

#116: Installing cl-unicode via quicklisp fails ----------------------------------------+----------------------------------- Reporter: vvoutilainen | Owner: somebody Type: defect | Status: new Priority: major | Milestone: 0.25 Component: other | Version: Keywords: quicklisp world domination | ----------------------------------------+----------------------------------- Here's the printout and a reproduction recipe: ================================================== ; Loading "cl-unicode" ... ;;; Parsing Unicode file UnicodeData.txt ;;; Parsing Unicode file Scripts.txt ;;; Parsing Unicode file Blocks.txt ;;; Parsing Unicode file PropList.txt ;;; Parsing Unicode file DerivedAge.txt ;;; Parsing Unicode file BidiMirroring.txt ;;; Parsing Unicode file Jamo.txt ;;; Building hash tables ;;; Writing source file methods.lisp ;;; Writing source file hash-tables.lisp ;;; Writing source file lists.lisp ;;; Writing source file derived-properties ;;; Parsing Unicode file DerivedCoreProperties.txtjava.lang.ClassFormatError: Unknown constant tag 41 in class file org/armedbear/lisp/ASDF_TMP_hash_tables_2 at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:634) at java.lang.ClassLoader.defineClass(ClassLoader.java:480) at org.armedbear.lisp.FaslClassLoader.findClass(FaslClassLoader.java:95) at org.armedbear.lisp.FaslClassLoader.loadClass(FaslClassLoader.java:77) at java.lang.ClassLoader.loadClass(ClassLoader.java:266) at java.lang.Class.getDeclaredConstructors0(Native Method) at java.lang.Class.privateGetDeclaredConstructors(Class.java:2406) at java.lang.Class.getConstructor0(Class.java:2716) at java.lang.Class.newInstance0(Class.java:343) at java.lang.Class.newInstance(Class.java:325) ... ================================================== Reproduce: 1. Install Quicklisp 2. (ql:quickload :cl-unicode) -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/116> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 7

[armedbear-ticket] [armedbear] #148: READTABLE-CASE :invert does not invert uninterned symbols
by armedbear 16 Aug '11

16 Aug '11

#148: READTABLE-CASE :invert does not invert uninterned symbols -----------------------------------+---------------------------------------- Reporter: mevenson | Owner: somebody Type: defect | Status: new Priority: major | Milestone: 0.26 Component: other | Version: 0.24 Keywords: readtable parenscript | -----------------------------------+---------------------------------------- [http://article.gmane.org/gmane.lisp.armedbear.devel/1891 Ole Arendt reports]: This prevents loading a newer parenscript, which uses an inverted readtable case via named-readtables: {{{ Armed Bear Common Lisp 0.26.0-dev-svn-13273 Java 1.6.0_17 Sun Microsystems Inc. Java HotSpot(TM) 64-Bit Server VM Low-level initialization completed in 0.712 seconds. Startup completed in 3.154 seconds. Type ":help" for a list of available commands. CL-USER(1): (setf (readtable-case *readtable*) :invert) :invert CL-USER(2): (string :cl) "CL" CL-USER(3): (string '#:cl) "cl" }}} -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/148> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 1

[armedbear-ticket] [armedbear] #141: Fix the SETF expander to work with APPLY for arbitrary function
by armedbear 07 Aug '11

07 Aug '11

#141: Fix the SETF expander to work with APPLY for arbitrary function ----------------------------+----------------------------------------------- Reporter: mevenson | Owner: somebody Type: defect | Status: new Priority: major | Milestone: 0.26 Component: other | Version: 0.24 Keywords: setf quicklisp | ----------------------------+----------------------------------------------- CL-CONTAINERS from Quicklist MAR2011 fails to compile because our SETF expander for APPLY doesn't work for functions other than #'AREF, #'BIT, and #'SBIT as can be seen [source:trunk/abcl/src/org/armedbear/lisp/late- setf.lisp#L90 by the ERROR generated by late-setf.lisp]. The SETF expansion for APPLY should work with an arbitrary function. -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/141> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 1

[armedbear-ticket] [armedbear] #96: Lambda list &rest compilation error
by armedbear 06 Aug '11

06 Aug '11

#96: Lambda list &rest compilation error -----------------------------+---------------------------------------------- Reporter: mevenson | Owner: ehuelsmann Type: defect | Status: new Priority: minor | Milestone: unscheduled Component: compiler | Version: Keywords: compiler lambda | -----------------------------+---------------------------------------------- The following lambda list {{{ (defun hashmap-to-hashtable (&key (k #'identity) &rest rest) (let ((foo))) }}} fails to compile with the error {{{ &REST/&BODY must be followed by a variable. }}} Reported by Alan Ruttenberg -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/96> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 3

[armedbear-ticket] [armedbear] #122: writeToString infrastructure doesn't support *PRINT-CIRCLE*
by armedbear 06 Aug '11

06 Aug '11

#122: writeToString infrastructure doesn't support *PRINT-CIRCLE* ------------------------+--------------------------------------------------- Reporter: ehuelsmann | Owner: nobody Type: defect | Status: new Priority: major | Milestone: Component: java | Version: Keywords: | ------------------------+--------------------------------------------------- From a reaction of mine to a mail by Kevin Reid: > I don't think it's a good idea to explicitly bind *print-circle* to > nil in anything debugging-related, including error printing, because > then it's a source of nontermination (silent until out of memory, if > the output is going to a string) if user code is working with circular > structure. That's a good point. Rather, it may even be better to explicitly bind it to T. This remark made me realize that our Java side writeToString actually doesn't support *PRINT-CIRCLE* which can be an issue when trying to debug ABCL before it has loaded the ERROR and PRINT-OBJECT infrastructures. -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/122> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 2

[armedbear-ticket] [armedbear] #160: Printing objects with "#<" in their readable representation fail to print readably
by armedbear 06 Aug '11

06 Aug '11

#160: Printing objects with "#<" in their readable representation fail to print readably ------------------------+--------------------------------------------------- Reporter: ehuelsmann | Owner: somebody Type: defect | Status: new Priority: major | Milestone: Component: CLOS | Version: Keywords: | ------------------------+--------------------------------------------------- (let ((s (gensym "#<")) (*print-readably* t)) (print s)) --> Error: Object cannot be printed readably However, the readable presentation of that symbol is #:|#<1|. -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/160> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 4

[armedbear-ticket] [armedbear] #147: *PRINT-CASE* setting affects compiler
by armedbear 06 Aug '11

06 Aug '11

#147: *PRINT-CASE* setting affects compiler ----------------------+----------------------------------------------------- Reporter: mevenson | Owner: ehuelsmann Type: defect | Status: new Priority: critical | Milestone: 0.26 Component: compiler | Version: 1.0 Keywords: compiler | ----------------------+----------------------------------------------------- As [http://article.gmane.org/gmane.lisp.armedbear.devel/1887 reported by Dan Corkill]: The compiler is badly affected with *PRINT-CASE* set to :DOWNCASE, seemingly failing to look up internal definitions. {{{ (in-package :cl-user) (eval-when (:compile-toplevel :load-toplevel :execute) (setf *print-case* ':downcase)) (defstruct rec a b) }}} -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/147> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 1

[armedbear-ticket] [armedbear] #158: Printing "#<abc>" fails when *PRINT-READABLY* non-NIL
by armedbear 06 Aug '11

06 Aug '11

#158: Printing "#<abc>" fails when *PRINT-READABLY* non-NIL ------------------------+--------------------------------------------------- Reporter: ehuelsmann | Owner: nobody Type: defect | Status: new Priority: major | Milestone: Component: libraries | Version: Keywords: | ------------------------+--------------------------------------------------- (let ((*print-readably* t)) (print "#<abc>")) --> Error: #<abc> cannot be printed readably However, I'm printing a string containing something which looks like an unreadable object. Not an unreadable object itself! -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/158> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 3

[armedbear-ticket] [armedbear] #131: LISP-IMPLEMENTATION-VERSION with svn information breaks SLIME.
by armedbear 05 Aug '11

05 Aug '11

#131: LISP-IMPLEMENTATION-VERSION with svn information breaks SLIME. ----------------------+----------------------------------------------------- Reporter: mevenson | Owner: mevenson Type: defect | Status: new Priority: major | Milestone: Component: CLOS | Version: Keywords: | ----------------------+----------------------------------------------------- Reported by ehu via #abcl. -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/131> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 5

[armedbear-ticket] [armedbear] #145: Support running ABCL on JamVM
by armedbear 02 Aug '11

02 Aug '11

#145: Support running ABCL on JamVM -----------------------------+---------------------------------------------- Reporter: mevenson | Owner: nobody Type: defect | Status: new Priority: major | Milestone: 0.26 Component: java | Version: 0.24 Keywords: jamvm classpath | -----------------------------+---------------------------------------------- A request to support ABCL running on the [http://jamvm.sourceforge.net/ JamVM]. This may be roughly equivalent to working through the idiosyncrasies of running with [http://www.gnu.org/software/classpath GNU classpath], as GCJ seems to give similar errors. -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/145> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 2

[armedbear-ticket] [armedbear] #149: Cannot load ASDF systems from *.asd definition in base of JAR hierarchy
by armedbear 02 Aug '11

02 Aug '11

#149: Cannot load ASDF systems from *.asd definition in base of JAR hierarchy -------------------------------+-------------------------------------------- Reporter: mevenson | Owner: mevenson Type: defect | Status: new Priority: minor | Milestone: 0.26 Component: other | Version: 1.0 Keywords: asdf url-pathname | -------------------------------+-------------------------------------------- For an ASDF definition packaged in a JAR file in the topmost directory, viz {{{ mama:~/work/abcl/bugs$ jar tfv trivial.jar 76 Thu May 12 13:58:30 CEST 2011 trivial.asd 52 Thu May 12 13:58:52 CEST 2011 trivial.lisp }}} The ASDF definition cannot be properly loaded after placing "jar:file:~/work/abcl/bugs/trivial.jar!/" in the ASDF:*CENTRAL-REGISTRY*. One can see that something has gone wrong in the ASDF/MERGE-PATHNAMES with URL-PATHNAMES as after the unsucessful load the following shows that ASDF has thrown away the JAR-PATHNAME reference {{{ CL-USER> (asdf:component-pathname (asdf:find-system :trivial)) #P"/Users/evenson/work/abcl/" }}} The workaround is simple: always package ASDF definition in at least one top-level directory, viz: {{{ mama:~/work/abcl/bugs$ jar tfv trivial.jar 0 Thu May 12 14:18:18 CEST 2011 META-INF/ 60 Thu May 12 14:18:18 CEST 2011 META-INF/MANIFEST.MF 0 Thu May 12 13:58:52 CEST 2011 trivial/ 76 Thu May 12 13:58:30 CEST 2011 trivial/trivial.asd 52 Thu May 12 13:58:52 CEST 2011 trivial/trivial.lisp }}} When I get a change, I'll go through the URL-PATHNAME code with ASDF to understand where this is breaking. -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/149> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 2

[armedbear-ticket] [armedbear] #56: Eliminate use of temporary files in COMPILE and COMPILE-FILE
by armedbear 02 Aug '11

02 Aug '11

#56: Eliminate use of temporary files in COMPILE and COMPILE-FILE -------------------------+-------------------------------------------------- Reporter: ehuelsmann | Owner: ehuelsmann Type: enhancement | Status: new Priority: major | Milestone: Component: compiler | Version: Keywords: | -------------------------+-------------------------------------------------- The functions COMPILE and COMPILE-FILE use temporary files for the class files generated by the compiler. However, COMPILE directly loads them back into memory and deletes the temp file, while COMPILE-FILE deletes the temp file after adding it to a ZIP archive. This ticket exists to indicate that infrastructure is required to better manage where output goes to, abstracting from the temp files. -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/56> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 7

[armedbear-ticket] [armedbear] #157: 0.26 ansi-test regressions
by armedbear 02 Aug '11

02 Aug '11

#157: 0.26 ansi-test regressions -----------------------------------+---------------------------------------- Reporter: vvoutilainen | Owner: ehuelsmann Type: defect | Status: new Priority: minor | Milestone: 0.27 Component: compiler | Version: Keywords: ansi-tests regression | -----------------------------------+---------------------------------------- Diff: -31 out of 21702 total tests failed: +36 out of 21702 total tests failed: (MULTIPLE-VALUE-PROG1.10 DEFGENERIC.ERROR.20 DEFGENERIC.ERROR.21 @@ -14566,8 +14629,9 @@ TYPE-OF.4 CHAR-UPCASE.2 CHAR-DOWNCASE.2 +CHAR-NAME.1 ENSURE-DIRECTORIES-EXIST.8 -PRINT.STRING.RANDOM.1 +PRINT.SYMBOL.RANDOM.2 PRINT.RANDOM-STATE.1 PPRINT-FILL.14 PPRINT-FILL.15 @@ -14576,11 +14640,15 @@ PPRINT-LOGICAL-BLOCK.17 PPRINT-POP.7 PPRINT-POP.8 +FORMAT.C.2A +FORMATTER.C.2A FORMAT.LOGICAL-BLOCK.CIRCLE.1 FORMAT.LOGICAL-BLOCK.CIRCLE.2 FORMAT.LOGICAL-BLOCK.CIRCLE.3 +SYNTAX.SHARP-BACKSLASH.6 +SYNTAX.SHARP-BACKSLASH.7 TRACE.8) -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/157> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 7

[armedbear-ticket] [armedbear] #156: Readtime macro compiler error
by armedbear 02 Aug '11

02 Aug '11

#156: Readtime macro compiler error ----------------------+----------------------------------------------------- Reporter: mevenson | Owner: ehuelsmann Type: defect | Status: new Priority: blocker | Milestone: 0.26 Component: compiler | Version: Keywords: | ----------------------+----------------------------------------------------- [http://article.gmane.org/gmane.lisp.armedbear.devel/1958 Binghe reports that Ironclad cannot be compiled any longer]. He distilled the problem to {{{ (defconstant a #.(make-array '(8 256) :element-type '(unsigned-byte 32) :initial-element 0)) }}} -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/156> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 4

[armedbear-ticket] [armedbear] #154: COMPILE-FILE-TEST-CONDITION.2A ansi compiled fails
by armedbear 13 Jul '11

13 Jul '11

#154: COMPILE-FILE-TEST-CONDITION.2A ansi compiled fails -----------------------------------------------+---------------------------- Reporter: mevenson | Owner: ehuelsmann Type: defect | Status: new Priority: blocker | Milestone: 0.26 Component: compiler | Version: Keywords: compiler ansi-compiled regression | -----------------------------------------------+---------------------------- Regression to fix before abcl-0.26.0 RC {{{ java.lang.StackOverflowError at java.lang.ThreadLocal.get(ThreadLocal.java:125) at org.armedbear.lisp.LispThread.currentThread(LispThread.java:70) at org.armedbear.lisp.typep_4.execute(typep.lisp:65) at org.armedbear.lisp.Symbol.execute(Symbol.java:801) at org.armedbear.lisp.LispThread.execute(LispThread.java:653) at org.armedbear.lisp.format_189.execute(format.lisp:1723) at org.armedbear.lisp.CompiledClosure.execute(CompiledClosure.java:112) at org.armedbear.lisp.Symbol.execute(Symbol.java:801) at org.armedbear.lisp.LispThread.execute(LispThread.java:653) at org.armedbear.lisp.print_unreadable_object_1.execute(print- unreadable-object.lisp:35) }}} -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/154> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 5

[armedbear-ticket] [armedbear] #151: LOAD fails for whitespace in JAR-PATHNAME
by armedbear 13 Jul '11

13 Jul '11

#151: LOAD fails for whitespace in JAR-PATHNAME ----------------------+----------------------------------------------------- Reporter: mevenson | Owner: somebody Type: defect | Status: new Priority: major | Milestone: Component: other | Version: Keywords: | ----------------------+----------------------------------------------------- Loading a FASL with a space in its name from a jar fails {{{ ;;; FAILS (load "jar:file:/Users/evenson/work/abcl/bugs/xx.jar!/xx/foo bar.abcl") }}} -- Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/151> armedbear <http://common-lisp.net/project/armedbear> armedbear

1 3