00:04:43 deepfire [~deepfire@80.92.100.69] has joined #ccl 00:13:05 -!- anRch [~markmilli@64.134.243.163] has quit [Quit: anRch] 00:30:37 rme_ [~rme@pool-70-106-131-228.chi01.dsl-w.verizon.net] has joined #ccl 00:31:47 -!- rme [rme@clozure-9AC31E29.chi.dsl-w.verizon.net] has quit [Ping timeout] 00:31:48 -!- rme_ is now known as rme 00:33:30 -!- rme [~rme@pool-70-105-114-192.chi.dsl-w.verizon.net] has quit [Ping timeout: 265 seconds] 00:33:30 -!- rme_ is now known as rme 01:05:15 -!- nurv [nurv@83.231.16.68] has quit [] 01:05:44 Phoodus [foo@174-22-192-234.phnx.qwest.net] has joined #ccl 01:08:02 -!- billstclair [~billstcla@unaffiliated/billstclair] has quit [Remote host closed the connection] 01:50:37 billstclair [~billstcla@gw3.tacwap.org] has joined #ccl 01:50:37 -!- billstclair [~billstcla@gw3.tacwap.org] has quit [Changing host] 01:50:37 billstclair [~billstcla@unaffiliated/billstclair] has joined #ccl 02:22:21 palter [~palter@c-75-68-177-225.hsd1.ma.comcast.net] has joined #ccl 02:22:36 -!- palter [~palter@c-75-68-177-225.hsd1.ma.comcast.net] has quit [Client Quit] 03:08:41 alms [~alms@64.214.179.14] has joined #ccl 03:54:35 bfulgham_ [~brent@adsl-69-234-96-102.dsl.irvnca.pacbell.net] has joined #ccl 04:25:45 -!- alms [~alms@64.214.179.14] has quit [Quit: alms] 05:37:30 -!- leo2007 [~leo@cpc1-cmbg13-0-0-cust596.cmbg.cable.ntl.com] has quit [Ping timeout: 265 seconds] 05:43:09 -!- rme [~rme@pool-70-106-131-228.chi01.dsl-w.verizon.net] has quit [Quit: rme] 07:25:52 rme [~rme@pool-70-106-131-228.chi01.dsl-w.verizon.net] has joined #ccl 07:50:22 -!- rme [rme@clozure-2CA44D4B.chi01.dsl-w.verizon.net] has quit [Quit: rme] 07:50:22 -!- rme [~rme@pool-70-106-131-228.chi01.dsl-w.verizon.net] has quit [Quit: rme] 09:31:44 nurv [nurv@83.231.87.201] has joined #ccl 09:31:50 Hi. 10:11:08 -!- billstclair [~billstcla@unaffiliated/billstclair] has quit [Remote host closed the connection] 10:13:32 billstclair [~billstcla@unaffiliated/billstclair] has joined #ccl 10:24:57 -!- clop [~jared@moat3.centtech.com] has quit [*.net *.split] 10:27:24 clop [~jared@moat3.centtech.com] has joined #ccl 10:57:57 alms [~alms@64.214.179.14] has joined #ccl 11:14:19 -!- sellout [~greg@c-24-128-48-180.hsd1.ma.comcast.net] has quit [*.net *.split] 11:19:27 leo2007 [~leo@cpc1-cmbg13-0-0-cust596.cmbg.cable.ntl.com] has joined #ccl 11:19:42 sellout [~greg@c-24-128-48-180.hsd1.ma.comcast.net] has joined #ccl 11:20:22 hello, last night I found out that I suddenly can't connect to a swank server running in ccl. 11:20:34 but I can if it is running in sbcl. 11:21:16 I am clueless about how to fix this problem. Any idea? 11:23:45 when emacs tries to connect to the ccl swank, it freezes with this in the echo area: error in process filter: open-network-stream: make client process failed: connection refused, :name, *lisp-output-stream*, :buffer, *cl-connection*, :host, 127.0.0.1, :service, 50896 11:24:07 the backtrace after hitting C-g is in http://paste.lisp.org/display/98944. 11:29:39 -!- alms [~alms@64.214.179.14] has quit [Quit: alms] 11:33:32 alms [~alms@64.214.179.14] has joined #ccl 11:39:55 leo2007: the obvious first question is are you sure the swank running in your CCL is the same as the slime.el running in your emacs 11:40:12 If you started it with m-x slime, then it is 11:40:23 If you loaded swank in CCL, then used m-x slime-connect, it may not be 11:40:25 you mean the CHANGELOG date? 11:40:41 I think that's what slime calls the "version" 11:41:16 sorry the swank server is on a remote machine but I make sure swank and slime are both update to date 11:41:25 ok 11:41:31 I thought you would, but have to ask 11:42:12 Which port are you using for the swank server? 11:42:17 Default on both sides? 11:43:39 billstclair: swank on 4001 and forward local 4007 to it 11:43:51 An ssh tunnel? 11:43:55 yes 11:44:13 4007:localhost:4001 ? 11:44:37 And does the same tunnel work for the SBCL swank listening on the same port on the same machine? 11:44:44 I did it in ssh/config with LocalForward 4007 localhost:4001 11:45:00 billstclair: yes, they work for sbcl. 11:45:13 ok. SO that gets rid of the things you likely already checked yourself 11:45:22 for ccl, I can connect if not using slime-repl. 11:45:47 Not that slime is very useful without slime-repl... 11:46:18 I was most confused when that was split out of the main slime 11:47:03 the hang happens with this setting (slime-setup '(slime-fancy slime-banner slime-asdf slime-indentation)) 11:47:11 in a emacs started with -q 11:48:04 Wait, does the hang happen with or without slime-repl? You said one, then the other. 11:48:27 with slime-repl 11:48:49 i.e. when I use (slime-setup '(slime-fancy slime-banner slime-asdf slime-indentation)) 11:49:03 So you just want to run lisp commands on the remote machine automatically from your emacs, but don't need a repl? 11:49:11 .ccl-init.lisp is pasted in http://paste.lisp.org/display/98944#1 11:49:21 -!- alms [~alms@64.214.179.14] has quit [Quit: alms] 11:51:45 Please ensure that SWANK::*SWANK-WIRE-PROTOCOL-VERSION* has the same value in both SBCL and CCL 11:52:15 I know that they're both up-to-date asdf-install version, but I want to see it for sure 11:53:11 billstclair: I symlink the slime dir in ccl and sbcl 11:53:18 Well, that would do it 11:53:27 Hard to deny 11:53:52 'fraid I'm not enough of a slime expert to take it any further. Slime mailing list time 11:54:00 Unless there's a #slime here 11:54:07 Have you asked in #lisp? 11:54:39 Well, there IS a #slime, but only sellout is there 11:55:04 And he's only there checking, like me. :) 11:56:03 could you help with one more thing? does ccl release the port it uses after I terminate it. 11:56:17 now I can't start sbcl because of this Socket error in "bind": EADDRINUSE (Address already in use) 11:57:13 I don't know, without spending as long as it would take you to chase down the exit code, but aren't ports released when a process exits? Or is there a delay? 11:58:23 gbyers might know, though 12:02:02 Looks like there IS a delay, and the new process needs to use SO_REUSEADDR if it doesn't want to wait for 2 minutes: http://stackoverflow.com/questions/548879/releasing-bound-ports-on-process-exit 12:02:17 And that dealy happens whether the old process closed explicitly or not 12:02:37 i find that ccl64 is using a different init script than ~/.ccl-init.lisp 12:02:50 but I don't know where that script is 12:03:00 my change in .ccl-init.lisp has no effect 12:03:04 Interesting. I never use init scripts so I don't know off the top of my head 12:03:17 Probably in the docs. Looking... 12:03:43 leo2007: I use "ccl-init.lisp" (no leading ".") 12:05:01 great! it was that file that causes all the trouble 12:05:48 docs say it uses ccl-init.lisp, then, if that doesn't exist, .ccl-init.lisp (after 1.2) 12:08:28 that was a fucking mistake that wasted several hours of mine. 12:08:49 but I am glad I can continue with remote development. 12:09:07 billstclair and sellout thank you for the help. 12:10:53 Glad it works now :) 12:12:32 ;) 12:15:57 -!- leo2007 [~leo@cpc1-cmbg13-0-0-cust596.cmbg.cable.ntl.com] has quit [Quit: reboot emacs] 12:18:24 alms [~alms@64.214.179.14] has joined #ccl 12:18:36 -!- alms [~alms@64.214.179.14] has quit [Client Quit] 12:56:16 leo2007 [~leo@cpc1-cmbg13-0-0-cust596.cmbg.cable.ntl.com] has joined #ccl 12:56:36 I am glad everything is now sorted. 12:57:10 My next step is to use the parallel library. 13:00:36 -!- sellout [~greg@c-24-128-48-180.hsd1.ma.comcast.net] has quit [*.net *.split] 13:06:40 sellout [~greg@c-24-128-48-180.hsd1.ma.comcast.net] has joined #ccl 13:18:39 for ccl, C-M-x still compiles the defun, right? In essence, it is not much different from C-c C-c. 13:24:25 -!- sellout [~greg@c-24-128-48-180.hsd1.ma.comcast.net] has quit [Quit: sellout] 13:25:10 sellout [~greg@c-24-128-48-180.hsd1.ma.comcast.net] has joined #ccl 13:34:13 leo2007: correct. The only drawback is that meta-. doesn't work on the definition afterwards 13:34:37 Not sure if C-c C-c is different in that regard. Never use it 13:44:12 leo2007 pasted "parallel testing" at http://paste.lisp.org/display/98953 13:45:02 I was able to use parallel to take advantage of multiple cores on a single machine. The timing seems a bit strange to me. See the output in 98953. 13:45:54 'time' seems incorrect in the second case. 13:49:58 the second time is the sum of time used by each core. The improve doesn't seem significant. 15:18:33 anRch [~markmilli@63.112.62.27] has joined #ccl 15:59:21 ccl Segmentation fault 16:00:20 folks, when I use ', quit' in slime repl to quit, ccl prints 'Segmentation fault'. Does this happen to you too? 16:03:42 rme [~rme@pool-70-106-132-157.chi01.dsl-w.verizon.net] has joined #ccl 16:14:32 -!- nurv [nurv@83.231.87.201] has quit [] 16:43:41 -!- anRch [~markmilli@63.112.62.27] has quit [Quit: anRch] 17:00:57 -!- Adlai [~Adlai@unaffiliated/adlai] has quit [Quit: ERC Version 5.3 (IRC client for Emacs)] 17:05:02 hello rme 17:08:08 I tried running fib and pfib from parallel.lisp, but the improvement doesn't seem significant enough. 17:23:40 anRch [~markmilli@64.134.71.109] has joined #ccl 18:52:07 -!- anRch [~markmilli@64.134.71.109] has quit [Quit: anRch] 18:55:31 nurv [nurv@62.32.144.157] has joined #ccl 18:55:41 Hi. 19:05:06 leo2007: fibonacci doesn't benefit from parallelism. 19:05:25 Although I suppose a stupid implementation could 19:05:46 Where you actually do a complete computation of fib(n-1) and fib(n-2) for fib(n) 19:09:39 (quit) in the slime-repl doesn't cause a segmentation fault for me, running CCL 1.5 in OS X 19:10:19 SWANK::*SWANK-WIRE-PROTOCOL-VERSION*, Value: "2009-10-12" 19:11:15 -!- billstclair [~billstcla@unaffiliated/billstclair] has quit [Remote host closed the connection] 19:12:12 billstclair [~billstcla@gw3.tacwap.org] has joined #ccl 19:12:12 -!- billstclair [~billstcla@gw3.tacwap.org] has quit [Changing host] 19:12:12 billstclair [~billstcla@unaffiliated/billstclair] has joined #ccl 19:36:40 anRch [~markmilli@64.134.69.171] has joined #ccl 20:30:47 -!- anRch [~markmilli@64.134.69.171] has quit [Ping timeout: 260 seconds] 20:34:56 billstclair: thanks. I suppose it is one of those cl-plplot bugs. 20:35:26 i use the implementation on this page http://userweb.cs.utexas.edu/users/ragerdl/parallelism/ 20:42:51 leo2007: well, that's the "stupid" implementation of fibonacci, so I'm surprised it isn't faster in parallel. Did you pick numbers big enough so that it takes multiple seconds without parallelism? 20:44:32 The results in http://paste.lisp.org/display/98953 20:44:39 took minutes to run. 20:45:39 Strange. I wonder if it's smart enough to not cons up more threads than there are processors 20:45:58 If it's doing that, I'm not surprised that you get a lot less than a 4x speedup 20:49:38 -!- billstclair [~billstcla@unaffiliated/billstclair] has quit [Remote host closed the connection] 21:02:50 billstclair [~billstcla@p-216-227-83-3.dsl1.rtr.chat.fpma.frpt.net] has joined #ccl 21:02:50 -!- billstclair [~billstcla@p-216-227-83-3.dsl1.rtr.chat.fpma.frpt.net] has quit [Changing host] 21:02:50 billstclair [~billstcla@unaffiliated/billstclair] has joined #ccl 21:27:35 billstclair: hi 21:28:39 so the reason that I haven't seen much improve on pfib is because the implementation isn't good enough, not because parallel.lisp? 22:47:06 hypno_ [~hypno@impulse2.gothiaso.com] has joined #ccl 22:54:00 -!- hypno [~hypno@impulse2.gothiaso.com] has quit [*.net *.split] 23:25:31 alms [~alms@64.214.179.14] has joined #ccl 23:25:35 -!- alms [~alms@64.214.179.14] has quit [Client Quit] 23:49:58 -!- rme [rme@clozure-941A5270.chi01.dsl-w.verizon.net] has quit [Quit: rme] 23:49:58 -!- rme [~rme@pool-70-106-132-157.chi01.dsl-w.verizon.net] has quit [Quit: rme]