gmane.lisp.cmucl.general

Re: Please explain this compiler note

Stelian Ionescu — 2008-11-19T17:57:59

the latter

Re: Please explain this compiler note

Didier Verna — 2008-11-19T17:45:34

Hmmm, I'm confused. The return value of DEFUN is the function name, right? Or do you mean that when CMU-CL creates the accessor function, it generates code to box the return value and /that/ is what triggers the note?

Re: Please explain this compiler note

Stelian Ionescu — 2008-11-19T16:58:22

On Wed, 2008-11-19 at 16:40 +0100, Didier Verna wrote: The return value of (DEFUN MYSTRUCT-SLOT (OBJECT) ...) : the value of the slot SLOT is boxed hence the compiler note.

Please explain this compiler note

Didier Verna — 2008-11-19T15:40:18

[Fwd: ILC]

Raymond Toy — 2008-10-29T13:04:44

In case you didn't already know, there's another Lisp conference coming up. Ray, who might go if he plans things out better this time than he did for OOPSLA.

Re: Mailing list issues?

Raymond Toy — 2008-10-16T18:54:52

Could you try that? The issue is the newly subscribed addresses do not receive messages from the list and cannot send messages to the list. (I assume the messages are sent, but they never appear on the list.) Thanks, Ray

Re: Mailing list issues?

Raymond Toy — 2008-10-16T18:41:32

Interesting. I have not (yet?) received any message from you from your gmail account. Ray

Re: Mailing list issues?

Martin Cracauer — 2008-10-16T17:59:54

Dunno, folks, works fine for me. I just subscribed to cmucl-imp using my gmail account. Subscription went smooth and I have received the test message I sent a couple minutes ago at that newly subscribed address. If you send me a list of problematic addresses I can slam them into listar by hand. Martin

Re: Mailing list issues?

Raymond Toy — 2008-10-16T17:36:47

Yes, that's my understanding. People subscribe, and they get mails saying they're subscribed. But they don't receive messages and can't send messages. Also, I had sent (private) email earlier to you at your cons.org address. Is that no longer really used? Is your itasoftware one better? Thanks for looking into this. Ray

Re: Mailing list issues?

Martin Cracauer — 2008-10-16T15:12:31

I'll look into this. All these spamfilter and security updates wreck the lists every now and then. I receive messesages just fine. Do you say that subscription is broken? Martin Raymond Toy wrote on Thu, Oct 16, 2008 at 10:50:36AM -0400:

Re: Mailing list issues?

Raymond Toy — 2008-10-13T15:42:23

Just a clarification. The mailing list appears ok, if you've previously received messages. But new subscribers appear to have problems. listar (or the mailing list software) says they're subscribed, but new subscribers apparently cannot send or receive messages, despite being subscribed. Ray

Mailing list issues?

Raymond Toy — 2008-10-13T13:35:42

Can someone check the mailing lists? It appears that subscriptions work but, in fact, you're not, because messages sent don't make to the list and new messages aren't forwarded to the new subscriber. Well, at least one person has mentioned to me that his subscription doesn't work. Thanks, Ray

CVS down

Raymond Toy — 2008-10-09T13:47:54

Just found out that common-lisp.net is being moved to a new server today (or yesterday). I guess the move is still in progress, so CVS is currently down. Trac is also down. common-lisp.net is up, though. It's being worked on. Ray

SSE2 support

Raymond Toy — 2008-10-06T14:29:52

While you're waiting for the 2008-10 snapshot, here's something new you can play with: SSE2 support for CMUCL. You can grab the (large) binary for Linux from This includes support for both x87 and sse2. (This idea was suggested by Carl.) The C runtime will try to determine if you machine supports sse2 and loads the sse2 core if it does. Otherwise, it loads the x87 core. There's a new command-line switch to allow you to select between the x87 or sse2 core if you want to force a certain core. "-fpu x87" selects the x87 core, and "-fpu sse2" selects the sse2 core. I've run some numerical tests and the sse2 core works just fine. I do not know if the sse2 core is faster or slower than the x87 core, but it does fix some issues with double-float support for x87. (See trac ticket #15, which now ret

Re: Undefined functions bug summary

Raymond Toy — 2008-10-06T13:19:13

These are all functions from either Gray streams or simple streams. Perhaps the way to get rid of the warnings is just to define dummy versions that will be replaced when Gray streams or simple streams are loaded. Ray

Undefined functions bug summary

Steven Edwards — 2008-10-05T17:29:49

When compiling with (speed 3) (safety 0) (space 0), I get: ; Warning: These functions are undefined: ; STREAM::%LISTEN STREAM::%READ-CHAR STREAM::%UNREAD-CHAR STREAM- LISTEN STREAM-READ-CHAR STREAM-UNREAD-CHAR ; because of references to: listen read-char unread-char (some with stream arguments, some without) However, the compiled code works fine. Banner: CMU Common Lisp 19e (19E), running on gail With core: /Users/sje/cmucl-19e-x86-darwin/lib/cmucl/lib/lisp.core Dumped on: Thu, 2008-05-01 20:38:02-04:00 on macmini See for support information. Loaded subsystems: Python 1.1, target Intel x86 CLOS based on Gerd's PCL 2004/04/14 03:32:47 Compilation banner: ; Python version 1.1, VM version Intel x86 on 05 OCT 08 01:22:45 pm.

Re: Error loading flexi-streams on CMUCL + Debian

Raymond Toy — 2008-10-01T21:43:06

Maybe you should have presented some of the other errors as well. Perhaps there were clues there? Anyway, I tried flexi-streams. I get an compilation error almost right away. (How did you not get the compilation errors?) The code assumes that the char-code-integer type is large enough to hold integers up to at least 65535 or so. But on CMUCL, char-code-limit is 256. Changing char-code-integer to be `(integer 0 65535) allows the code to compile. It passes a fair number of tests, but I have no idea if this is correct or not. Perhaps you can ask the on the flexi-streams lists for some more information. Ray

Re: Error loading flexi-streams on CMUCL + Debian

Raymond Toy — 2008-09-30T12:34:24

That usually means the fasl file (ascii.x86f) is empty. Something else has happened to cause the fasl to be empty. Are there other errors in the log that you didn't send? Is the disk full? I used flexi-streams a while back, and it worked. Can't remember what version though. Ray

Error loading flexi-streams on CMUCL + Debian

Watt Poosanguansit — 2008-09-30T01:40:36

I am new to CMUCL and flexi-streams. I tried to load the library and I got the message below. I have asked this on flexi-streams list and I was told this might be a better place since this might have to do with how CMUCL load the files. Any help is appreciated. ; loading system definition from ; /usr/local/asdf-install/site-systems/flexi-streams.asd into ; # ;; Loading #P"/usr/local/asdf-install/site/flexi-streams-1.0.7/flexi-streams.asd". ; registering # as FLEXI-STREAMS ; registering # as FLEXI-STREAMS-TEST ; Compiling LAMBDA (.PV-CELL. .NEXT-METHOD-CALL. O C): ; Compiling Top-Level Form: ;; Loading #P"/var/cache/common-lisp-controller/1000/cmucl/local/usr/local/asdf-install/site/flexi-streams-1.0.7/packages.x86f". ;; Loading #P"/var/cache/common-lisp-controller/1000/cmucl/local/usr/local/asdf-install/site/flexi-streams-1.0.7/mapping.x86f". Error in function LISP::INTERNAL-LOAD: File has a fasl file type,

Re: Another stumper compilation diagnostic

Steven Edwards — 2008-09-26T01:18:20

One of the goals is to minimize the number of complaints issue by cmucl when loading and compiling. In this I have made some progress as the compilation process that once made 9,000+ notes now outputs only some 1,200 squawks. I hope that within a month or two that I'll have a beta ready; I'll make an announcement here and so the adventuresome may take a crack at any remaining compilation objections. On Sep 25, 2008, at 1:18 PM, Raymond Toy wrote:

Re: Another stumper compilation diagnostic

Raymond Toy — 2008-09-25T17:18:33

My guess. nthcdr is declared maybe-inline. Since speed > space (or maybe space = 0 or something like that), nthcdr is inlined. And that happens before the deftransform for nthcdr is ever gets a chance. Easy enough to put an inhibit-warnings in the offending part of nthcdr. Not sure if we really want to. Or just don't compile the code with speed 3 and space 0. I've never really noticed much speed up with speed 3 on code that manipulates lists. But I don't manipulates lists that much. Ray