April 2015 - armedbear-devel - mailman3.common-lisp.net

Re: [armedbear-devel] Site is down
by Victor 08 Apr '15

08 Apr '15

On Wed, 09 Oct 2013 16:19:45 +0300, Victor <bobbie(a)ua.fm> wrote: > On Wed, 09 Oct 2013 16:11:34 +0300, Erik Huelsmann <ehuels(a)gmail.com> wrote: > >> Thanks for the heads-up. The site should be up again. > > Hi Erik, > > the server/host is now up on the internet again but instead of a nice Welcome page it shows a directory listing that reminds me of common-lisp.net before its upgrade. The site is back again. Thanks! > > Thanks, > Victor > > >> >> >> >> On Wed, Oct 9, 2013 at 2:17 PM, Victor <bobbie(a)ua.fm> wrote: >> >>> Hi, >>> >>> I noticed that http://armedbear.org/abcl.html points to the >>> Common-Lisp.net project page that redirects to www.abcl.org that is >>> currently down. >>> >>> Is it possible either to restore the site or turn the redirect off? >>> >>> Thanks, >>> Victor >>> >>>

1 0

[armedbear-devel] abcl-1.2.0 RC 0
by Mark Evenson 08 Apr '15

08 Apr '15

Live from the floor of ECLM 2013, [Binaries for the first release candidate for abcl-1.2.0][abcl-1.2.0-rc-0] have been uploaded and signed by <evenson.not.org(a)gmail.com>. For reasons that aren't entirely clear, the size of the archive has increased to 10 Mib. I'm not sure if this has been just a slow creep, or is related to the recent conversion of CLOS infrastructure from Java to Lisp. Please test if you can, letting us know if you have problems. [branch for 1.2.0]: http://abcl.org/svn/branches/1.2.0 [abcl-1.2.0-rc-0]: http://abcl.org/releases/1.2.0/rc-0

1 1

[armedbear-devel] Problem in CLOS MOP in abcl 1.2.0
by Pascal Costanza 08 Apr '15

08 Apr '15

Hi, There is a problem in the MOP implementation in abcl 1.2.0: It seems that the parameter list for std-find-method-combination has changed, but the corresponding :initform for :method-combination for standard-generic-function has not been updated to reflect this. I now get an error that std-find-method-combination gets the wrong number of arguments in my test suites. I don't have a good idea how to work around this problem in Closer to MOP, so I believe I cannot officially declare support for abcl 1.2.0. Another recommendation: The *features* list currently doesn't provide a way to detect the version of abcl. Most Common Lisp implementation have one convention or the other to encode this information. If I had a workaround for the above problem, detecting the version via *features* would allow me to provide a version of Closer to MOP that works with several versions of abcl. (This may, however, not be as crucial as for the commercial implementations.) Best, Pascal -- Pascal Costanza

2 1

[armedbear-devel] Compiler loses lexical macro in (eval-when (:compile-toplevel ...))
by Douglas Katzman 08 Apr '15

08 Apr '15

Hi. This code fragment works with (LOAD "/tmp/foo.lisp") but not (COMPILE-FILE "/tmp/foo.lisp") (eval-when (:compile-toplevel :load-toplevel :execute) (defvar *count* 0) (macrolet ((something (sym) `(setf (get ,sym 'uniqueid) (incf *count*)))) (defun register-it (x) (something x)))) (eval-when (:compile-toplevel :execute) (format t "~&OK so far~%") (register-it :foo)) (eval-when (:compile-toplevel :execute) (format t "~&Got ~D~%" (symbol-plist :foo))) Armed Bear Common Lisp 1.3.0 Java 1.7.0_51 Oracle Corporation Java HotSpot(TM) 64-Bit Server VM Low-level initialization completed in 0.258 seconds. Startup completed in 1.231 seconds. Type ":help" for a list of available commands. CL-USER(1): (compile-file "/tmp/foo.lisp") ; Compiling /private/tmp/foo.lisp ... ; (DEFVAR *COUNT* ...) ; (DEFUN REGISTER-IT ...) OK so far #<THREAD "interpreter" {3A284BEE}>: Debugger invoked on condition of type UNDEFINED-FUNCTION The function SOMETHING is undefined. Restarts: ...

2 1

[armedbear-devel] abcl-1.3.0 released
by Mark Evenson 08 Apr '15

08 Apr '15

http://abcl.org/releases/1.3.0 abcl-1.3.0 is a feature release. 15-MAR-2014 ## Features * Make LispStackFrame.UNAVAILABLE_ARG a singleton object, and lazily create the little used portions of the Lisp stack. Aggressively cache and control the use of memory by the underlying Lisp stack frame representation by introducing the private LispThread.StackFrame and LispThread.StackSegments classes. Contributed by Dmitry Nadezhin. LispStackFrame object are allocated on every LispThread.execute(...) . However, they are seldom [accessed] ([... verify via] inspect[tion of the] stack trace). This patch delays allocation of LispStackFrame? objects until they are requested. Raw information about stack frames is stored in stack. Stack is an Object[] array (more precisely a list of [...]4 [Mib] Object[] arrays). ME: We are going to need a way to try to less agressively grab 4Mib chunks in low memory situations. Memory profiling of ABCL shows that the classes with largest allocation count are org.armedbear.lisp.LispStackFrame and org.armedbear.lisp.LispStackFrame.UnavailableArgument. Contributed by Dmitry Nadezhin. [r14572]: http://abcl.org/trac/changeset/14572 [r14579]: http://abcl.org/trac/changeset/14579 * ASDF 3.0.1.94 shipped with the implementation * per function call stack and memory exception handler in CL:COMPILE Inline calls to jrun-exception-protected (used by handler-bind to catch out of memory conditions). This commit saves generation roughly 50 cls files. [r14552]: http://abcl.org/trac/changeset/14552 * SYS:SHA256 audited The functionality if the SYS:SHA256 algorithim has been audited for use on inputs of single for files with recently shipping ORCL Java 7 implementations (through jdk-1.7.0_51). [r14582]: http://abcl.org/trac/changeset/14582 * Connect to NetBeans controlled JDWP via SLIME The Netbeans IDE configuration now includes a way to connect to the running-under-jdb ABCL via SLIME. One needs a version of SLIME able to be loaded from its 'swank.asd' definition. * Install 'abcl.jar' and 'abcl-contrib.jar' locally as Maven artifacts The Ant `abcl.mvn.install` target now installs build artifacts into the local Maven repository (Olof-Joachim Frahm) [r14579]: http://abcl.org/trac/changeset/14606 ## Compatibility * CL:DIRECTORY The implementation specific :RESOLVE-SYMLINKS argument to the ANSI DIRECTORY function has been changed to nil. This implements behavior closer to SBCL and guarantees that a DIRECTORY operation will not signal a file error. [r14619]: http://abcl.org/trac/changeset/14619 [ticket-340]: http://abcl.org/trac/ticket/340 ## Fixes * Fix CL:SLEEP for intervals less than a millisecond. For intervals less than or equal to a nanosecond, including an interval of zero, the current thread merely yields execution to other threads. [r14632]: http://abcl.org/trac/changeset/14632 ## Tested ### "Java_HotSpot(TM)_64-Bit_Server_VM-Oracle_Corporation-1.7.0_51-b13" "x86_64-Mac_OS_X-10.9.1" ### "Java_HotSpot(TM)_64-Bit_Server_VM-Oracle_Corporation-1.8.0-b129" "x86_64-Mac_OS_X-10.9.2" ## Contrib #### abcl-asdf * Now working with both Maven 3.0.x and 3.1.x. Thanks to Anton for the help! [ticket-328]: http://abcl.org/trac/ticket/328 * cache Maven dependency resolution to avoid repeated lookups. Instead of calling ABCL-ASDF:RESOLVE in both the ASDF COMPILE-OP and LOAD-OP, we now cache the result of invocation in COMPILE-OP and add this value in the LOAD-OP phase. Contributed by Cyrus Harmon. [r14631]: http://abcl.org/trac/changeset/14631 #### jna Now references jna-4.0.0. Some incompatibility with CFFI ([in progress with fixing upstream][cffi-easye]). [cffi-easye]: http://github.com/easye/cffi/

5 16

[armedbear-devel] Why field LispStatckFrame.UNAVAILABLE_ARG is not static ?
by Dmitry Nadezhin 08 Apr '15

08 Apr '15

Memory profiling of ABCL shows that the classes with largest allocation count are LispStackFrame and LispStackFrame.UnavailableArgument . It seems to me that LispStatckFrame.UNAVAILABLE_ARG can be a singleton object, can't it ? =================================================================== --- LispStackFrame.java (revision 14571) +++ LispStackFrame.java (working copy) @@ -44,7 +44,7 @@ private final LispObject third; private final LispObject[] args; - private final class UnavailableArgument extends LispObject + private static final class UnavailableArgument extends LispObject { public UnavailableArgument () { } @Override @@ -53,7 +53,7 @@ } } - private final LispObject UNAVAILABLE_ARG = new UnavailableArgument(); + private static final LispObject UNAVAILABLE_ARG = new UnavailableArgument(); public LispStackFrame(LispObject operator) { ====================================================================

2 1

[armedbear-devel] Lazy allocation of LispStackFrames
by Dmitry Nadezhin 08 Apr '15

08 Apr '15

LispStackFrame object are allocated on every LispThread.execute(...) . However, they are seldom (to inspect stack trace). This patch delays allocation of LispStackFrame objects until they are requested. Raw information about stack frames is stored in stack. Stack is an Object[] array ( more precisely a list of 8 MB Object[] arrays ).

3 3

[armedbear-devel] CLOS for ABCL based on interpreted Closette?
by ubikation _ 08 Apr '15

08 Apr '15

I've been trying to read AMOP and looking at the Closette code. It seems to me that ABCL uses Closette for CLOS... but the original Xerox code seems to explicitly warn against using it for compiled CLOS. I was just wondering if this is perhaps the reason for the performance issues of CLOS in ABCL. Do other CL implementations use Closette? The text is "Load this source file directly, rather than trying to compile it." from here: http://homepage.stat.uiowa.edu/~luke/xls/xlispstat/other/closette/closette.… Thanks!

1 0

[armedbear-devel] Bug report: non-standard metaclass causes aberrant behaviour
by William Hounslow 08 Apr '15

08 Apr '15

Dear maintainers #1 a user-defined allocate-instance method is not called at all #2 slot-missing is called with a slot-name of nil #3 update-dependent is not being applied to its keyword arguments Best regards William "1.2.1" "Java_HotSpot(TM)_Client_VM-Oracle_Corporation-1.7.0_17-b02" "x86-Windows_7-6.1" ;;;#1 CL-USER(2): (defclass quux-class (standard-class) ()) #<STANDARD-CLASS QUUX-CLASS {D2A36B}> CL-USER(3): (defmethod allocate-instance :after ((class quux-class) &rest initargs) (format t "allocated ~S~%" class)) #<STANDARD-METHOD ALLOCATE-INSTANCE :AFTER (QUUX-CLASS) {14A0B92}> CL-USER(4): (defclass quux nil (bar) (:metaclass quux-class)) #<QUUX-CLASS QUUX {50039B}> CL-USER(5): (make-instance *) #<QUUX {B2D899}> CL-USER(6): (inspect (fdefinition 'allocate-instance)) 0 LAYOUT -----------> #<LAYOUT {BEF803}> 1 NAME -------------> ALLOCATE-INSTANCE 2 LAMBDA-LIST ------> (CLASS &REST ...) 3 REQUIRED-ARGS ----> (CLASS) 4 OPTIONAL-ARGS ----> NIL 5 INITIAL-METHODS --> NIL 6 METHODS ----------> (#<STANDARD-METHOD ALLOCATE-INSTANCE :AFTER (QUUX-CLASS) {14A0B92}> #<STANDARD-METHOD ALLOCATE-INSTANCE :BEFORE (CLASS) {18C9692}> ...) 7 METHOD-CLASS -----> #<STANDARD-CLASS STANDARD-METHOD {A801B0}> 8 %METHOD-COMBINATION -> #<METHOD-COMBINATION STANDARD {F167BB}> 9 ARGUMENT-PRECEDENCE-ORDER -> (CLASS) 10 DECLARATIONS -----> NIL 11 CLASSES-TO-EMF-TABLE -> #<EQUAL HASH-TABLE 0 entries, 11 buckets {D15EE4}> 12 %DOCUMENTATION ---> NIL ;;;#2 CL-USER(11): (make-instance 'quux) #<QUUX {F2AE7E}> CL-USER(12): (slot-value * 'baz) #<THREAD "interpreter" {1A2FE4D}>: Debugger invoked on condition of type SIMPLE-ERROR The slot NIL is missing from the class #<QUUX-CLASS QUUX {50039B}>. Restarts: 0: TOP-LEVEL Return to top level. ;;;#3 CL-USER(2): (defclass foo-class (standard-class) ()) #<STANDARD-CLASS FOO-CLASS {14A123F}> CL-USER(3): (defclass foo-dep () ()) #<STANDARD-CLASS FOO-DEP {145B486}> CL-USER(4): (defmethod mop:update-dependent ((class foo-class) (dep foo-dep) &key direct-slots &allow-other-keys)) #<STANDARD-METHOD MOP:UPDATE-DEPENDENT (FOO-CLASS FOO-DEP) {155388B}> CL-USER(5): (defclass foo () (bar) (:metaclass foo-class)) #<FOO-CLASS FOO {25D10A}> CL-USER(6): (mop:add-dependent * (make-instance 'foo-dep)) (#<FOO-DEP {F167BB}>) CL-USER(7): (trace mop:update-dependent) (MOP:UPDATE-DEPENDENT) CL-USER(8): (defclass foo () (bar baz) (:metaclass foo-class)) 0: (MOP:UPDATE-DEPENDENT #<FOO-CLASS {25D10A}> #<FOO-DEP {F167BB}> (:DIRECT-SUPERCLASSES NIL :DIRECT-SUPERCLASSES NIL DIRECT-SLOTS ((:NAME BAR) (:NAME BAZ)))) #<THREAD "interpreter" {886140}>: Debugger invoked on condition of type PROGRAM-ERROR Odd number of keyword arguments. Restarts: 0: TOP-LEVEL Return to top level.

2 1

[armedbear-devel] Email version of list?
by Steve Nunez 08 Apr '15

08 Apr '15

Hope this makes it through. It's not easy trying to find out where to sign up for the ABCL list. Does anyone know where this is done? This silly gmane web interface is complaining about lines longer than 80 characters.

3 3