armedbear-devel

armedbear-devel@common-lisp.net

1202 discussions

[armedbear-devel] BUG: JVM stack inconsistency triggered by compiler
by Eric Marsden 11 Jul '12

11 Jul '12

Hi, CL-USER(50): (lisp-implementation-version) "1.1.0-dev-svn-13998M" CL-USER(51): (lambda (a b c) (declare (optimize (safety 0))) (ash 3 (min 2 (the integer (block b (catch 'ct a)))))) #<FUNCTION (LAMBDA (A B C)) {374FB6BE}> CL-USER(52): (compile nil *) ; Caught STYLE-WARNING: ; The variable B is defined but never used. ; Caught STYLE-WARNING: ; The variable C is defined but never used. #<THREAD "interpreter" {5D4AAA93}>: Debugger invoked on condition of type INTERNAL-COMPILER-ERROR Stack inconsistency detected in NIL at index 36: found 2, expected 1. Restarts: 0: CONTINUE Eventually use interpreted form instead 1: TOP-LEVEL Return to top level. -- Eric Marsden

2 1

[armedbear-devel] BUG: threads:mailbox-send
by Uchida Yasuo 05 Jul '12

05 Jul '12

Hi folks, The function threads:mailbox-send seems not working. In the example below, (threads:mailbox-peek mbox) returns NIL. It should be "item". The attatched patch fixes this problem. Armed Bear Common Lisp 1.1.0-dev-svn-13992 Java 1.6.0_24 Sun Microsystems Inc. OpenJDK 64-Bit Server VM Low-level initialization completed in 1.396 seconds. Startup completed in 4.0 seconds. Type ":help" for a list of available commands. CL-USER(1): (setf mbox (threads:make-mailbox)) #S(MAILBOX :QUEUE NIL) CL-USER(2): (threads:mailbox-send mbox "item") NIL CL-USER(3): (threads:mailbox-peek mbox) NIL T CL-USER(4): Many thanks. -- Yasuo Uchida

2 1

[armedbear-devel] asdf::*OPERATING-SYSTEM* => :solaris for (LISP-IMPLEMENTATION-VERSION) => "1.0.1-svn-13750-13751"
by Alan Ruttenberg 28 Jun '12

28 Jun '12

Don't know if this is fixed in a later version, but I was noticing asdf put my binaries in an odd-looking directory. -Alan

2 1

[armedbear-devel] Fwd: How to compile and run Maxima with ABCL?
by Phuc Luoi 24 Jun '12

24 Jun '12

---------- Forwarded message ---------- From: Phuc Luoi <phucluoi(a)gmail.com> Date: Tue, Jun 19, 2012 at 12:51 PM Subject: Re: [armedbear-devel] How to compile and run Maxima with ABCL? To: Robert Dodier <robert.dodier(a)gmail.com> Thanks for your answer. I tried this and got these errors: Can't intern zero-length symbol. Restarts: 0: RETRY Retry compiling #<ASDF:CL-SOURCE-FILE "maxima" "utilities" "mformt">. 1: ACCEPT Continue, treating compiling #<ASDF:CL-SOURCE-FILE "maxima" "utilities" "mformt"> as having been successful. 2: TOP-LEVEL Return to top level. by compiling the file /maxima-5.27.0/src/mformt.lisp (step 9) I have choose the option 1 to accept this. I got some more errors by compiling. After all I got Out of memory PermGen space Restarts: 0: TOP-LEVEL Return to top level. and abcl did not compiled maxima. Can you tell me why I got these error? And how can repair them? On Tue, Jun 19, 2012 at 5:04 AM, Robert Dodier <robert.dodier(a)gmail.com> wrote: > On 2012-06-16, Phuc Luoi <phucluoi(a)gmail.com> wrote: > >> How can I compile and run Maxima with ABCL? > > (1) Unpack a Maxima tarball. > http://sourceforge.net/projects/maxima and follow links to download page. > Look for "Maxima-source". > > (2) cd /path/to/maxima-5.27.0 > > (3) java -jar /path/to/abcl.jar > > (4) (configure) ;; you can probably accept defaults for most/all questions > > (5) (quit) > > (6) cd src > > (7) java -jar /path/to/abcl.jar > > (8) (require 'asdf) > > (9) (asdf:operate 'asdf:load-op :maxima) > > (10) (quit) > > (11) java -jar /path/to/abcl.jar > > (12) (require 'asdf) > > (13) (asdf:operate 'asdf:load-op :maxima) ;; yes, same as (9) > > (14) (cl-user::run) ;; should bring up Maxima banner & input prompt > > >> Furthermore can I emmbed maxima in a Java Programm with ABCL? > > Yes. I've appended an example program. Command line to compile it: > > javac -cp /path/to/abcl.jar -d /path/to/compiled/class abcl_maxima.java > > To execute it: (you must be in the Maxima src directory) > > java -cp /path/to/compiled/class:/path/to/abcl.jar abcl_maxima > > I get: (takes a minute or two to load Maxima) > > loading Maxima ... finished. > x.getClass => class org.armedbear.lisp.Cons > x = org.armedbear.lisp.Cons@1748ba8 > x.javaInstance => org.armedbear.lisp.Cons@1748ba8 > x.javaInstance.getClass => class org.armedbear.lisp.Cons > 4 factors of 12341234 > factor: 2, multiplicity: 1 > factor: 73, multiplicity: 1 > factor: 137, multiplicity: 1 > factor: 617, multiplicity: 1 > > > Note that all user functions have names which begin with dollar sign. > E.g. user function ifactors <==> $IFACTORS in Lisp > > If you need help with Lisp programming for Maxima, ask questions on the > mailing list. See: http://maxima.sourceforge.net/maximalist.html > > Hope this helps, have fun, & good luck. > > Robert Dodier > > PS. Example program abcl_maxima.java: > > // abcl_maxima.java -- example program for calling Maxima from Java via ABCL > // copyright 2012 by Robert Dodier > // I release this work under terms of the GNU General Public License > > import org.armedbear.lisp.Interpreter; > import org.armedbear.lisp.Package; > import org.armedbear.lisp.Packages; > import org.armedbear.lisp.Symbol; > import org.armedbear.lisp.Function; > import org.armedbear.lisp.LispObject; > import org.armedbear.lisp.Fixnum; > import org.armedbear.lisp.Bignum; > import org.armedbear.lisp.Cons; > > public class abcl_maxima > { > public static void main (String [] args) throws Exception > { > int a; > > if (args.length > 0) > a = Integer.parseInt (args [0]); > else > a = 12341234; > > Interpreter I = Interpreter.createInstance (); > System.out.print ("loading Maxima ... "); > I.eval ("(require 'asdf)"); > I.eval ("(asdf:operate 'asdf:load-op :maxima)"); > System.out.println ("finished."); > Package P = Packages.findPackage ("MAXIMA"); > > // java.util.List <Symbol> L = P.getAccessibleSymbols (); > // for (Symbol S : L) > // { > // if (P.equals (S.getPackage ())) > // System.out.println (S.toString ()); > // } > > Symbol S = P.findAccessibleSymbol ("$IFACTORS"); > Function F = (Function) S.getSymbolFunction (); > LispObject x = Bignum.getInstance (a); > x = F.execute (x); > System.out.println ("x.getClass => " + x.getClass ()); > System.out.println ("x = " + x); > System.out.println ("x.javaInstance => " + x.javaInstance ()); > System.out.println ("x.javaInstance.getClass => " + x.javaInstance () . getClass ()); > > int n = ((Cons) x).length (); > System.out.println ((n - 1) + " factors of " + a); > > for (int i = 1; i < n; i++) > { > Cons x1 = (Cons) ((Cons) x).NTH (i); > Fixnum f = (Fixnum) x1.NTH (1); > Fixnum m = (Fixnum) x1.NTH (2); > System.out.println ("factor: " + f.intValue () + ", multiplicity: " + m.intValue ()); > } > } > } > > > _______________________________________________ > armedbear-devel mailing list > armedbear-devel(a)common-lisp.net > http://lists.common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel

4 16

[armedbear-devel] Does ABCL reload abcl.jar after it starts up?
by Marshall 21 Jun '12

21 Jun '12

I have a quick (I hope) question. Does ABCL reload abcl.jar after it starts up? Or do something else unusual with the jar once it's running? Context: I'm exploring using ABCL as an add-on to NetLogo, an agent-based modeling environment. (It might be more correct to say that I'm using NetLogo as an add-on to ABCL, since the primary code is in Lisp.) With the add-on method, NetLogo "extensions", one usually doesn't have to tell NetLogo where additional jars such as abcl.jar can be found. As long as they're in the extension's own directory, NetLogo will find the extra jars. This is apparently due to a little bit of voodoo that NetLogo engages in. However, in the case of my ABCL extension, NetLogo will load the extension, but then generate an error when I invoke ABCL via Interpreter.evaluate(). The problem is avoided if specify abcl.jar in the classpath explicitly, either on the command line (undesirable for NetLogo), or by adding abcl.jar to the classpath in Java (which works fine--so that's what I'm doing). Just curious about what ABCL is doing--thanks. (The ABCL NetLogo extension is very simple, now that I've figured out the details, and seems to be working beautifully, by the way. I'm surprised that there haven't been some glitches. It just works.) Marshall Abrams mabrams(a)uab.edu

2 1

[armedbear-devel] How to compile and run Maxima with ABCL?
by Phuc Luoi 18 Jun '12

18 Jun '12

Hello, How can I compile and run Maxima with ABCL? Furthermore can I emmbed maxima in a Java Programm with ABCL? Hong Phuc

2 1

[armedbear-devel] asdf 2.22 released
by Faré 13 Jun '12

13 Jun '12

I am pleased to announce the release of ASDF 2.22. Since previous release 2.21, the changes are as follow: * require is now mapped to the recently defined require-system, not to load-system anymore. * more sensible inheritance semantics for default-component-class, which can be either a class or a class name. (hat tip to Nikodemus) * accept wildcards in directory-files for physical pathnames. (hat tip to Erik Pearson). These changes are few and subtle, but nonetheless significant to those who'd use these features. As usual, developers, please test and enjoy, vendors, please update your implementation or distribution. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Pyramid schemes are illegal. Social Security is a pyramid scheme.

2 1

[armedbear-devel] jfli-abcl revisited
by Alex Mizrahi 12 Jun '12

12 Jun '12

hi Some people mentioned that keeping jfli interface is desirable. Also I've noticed a problem with Ole's version: java array accessor (jref) doesn't do boxing correctly. It isn't a big deal, but I kinda used that functionality, and I have no idea what motivated those changes so I don't know to to fix them correctly. So I went back to original jfli-abcl version by Andras Simon and did minimal amount of changes to make it work with new version. Also there are several conservative improvements. Here it is: https://gist.github.com/2916760#file_jfli.lisp And here's a diff against jfli-abcl.lisp still available on Andras' site: https://gist.github.com/2916760#file_jfli_abcl.diff (This one: http://www.math.bme.hu/~asimon/lisp/jfli-abcl.tar ) Here's a description of changes: 1. make-immediate-object is deprecated now, so we use java:+null+ and friends 2. boxing extension by A. Vodonosov is described in comment 3. ensure-java-class was renamed to %ensure-java-class to avoid collision with java:ensure-java-class which does completely different thing. (I thought about shadowing it, but I think renaming makes it clearer.) 4. support for both int and long in overloads (or however they are called in Java) 5. new-class functionality was commented out because abcl-side interface have changed. (together with its helper jrc) As I understand, Alessio already reimplemented jnew-runtime-class, so we just need some brave soul to adapt code to new APi and implement missing parts This isn't particularly hard, I think, but I'm not interested in new-class at all, so I wouldn't do this. And for the sake of completeness here's diff between original jfli-abcl and Ole's version: https://gist.github.com/2916945 It seems that the major difference is "Ripped out CLOS mirror support". I have no idea if 'CLOS mirror support' is required according to jfli spec or it is useless. Also there is a lot of refactoring. Which is great, but it can break things... So again, unless somebody has resources to check Ole's changes and verify that they adhere to jfli documentation, I recommend replacing it with my 'conservative' version in ABCL's contrib repo. Also, I've noticed that jfli maintainer said it would be cool to merge different versions, but I don't think it's necessary: the only common part is defpackage, pretty much all the code is specific to ABCL. (This was true for old jfli version, at least.) So it's better to treat jfli as a specification rather than as a library.

2 1

[armedbear-devel] Figuring out the provenance of trunk
by Mark Evenson 11 Jun '12

11 Jun '12

Over the course of maintaining the Bear, it has become clear to me that we have pieces of code in trunk whose original licensing terms indicate that their author should be contacted as to their status, especially when they would conflict with the terms we distribute under, namely those of the GNU Public License. Recently I discovered such a licensing lacunae [in working with Jorge Tavares to patch the CL:SORT and CL:STABLE-SORT routines][1], that 'sort.lisp' contains code that has both SBCL and ECL code attributions. Are we in violation of anything here? Dunno. But we certainly have *lots* of SBCL tucked into our tree… We obviously need an estimate of our non-compliance. As a first step, it seems useful to construct/use a tool that allows us to establish provenance of all commits to ABCL trunk. With this history in hand, we can start figuring out the set of all authors to work through potential conflicts. A fair amount of work for a non-specialist, but anyone who does this regularly should have an analysis toolset lying around that they could apply to [ABCL trunk][2]. Is there a language lawyer geek in the house? [1]: http://trac.common-lisp.net/armedbear/ticket/196 [2]: https://code.google.com/p/abcl-dynamic-install/source/browse/ -- "A screaming comes across the sky. It has happened before, but there is nothing to compare it to now."

3 3

[armedbear-devel] Patch to quicklisp/cffi-0.7.1 for abcl-1.1.0-dev
by Mark Evenson 30 May '12

30 May '12

Mebbe [this can help somewhat with the problems loading JNA automatically for CFFI on ABCL][1]. I still need to figure out exactly what is broken under which JVM/OS combinations. Interesting stuff in analyzing regressions. [1]: http://slack.net/~evenson/quicklisp/cffi-abcl-1.1.0-dev-20120530a.patch -- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now."

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

armedbear-devel