00:01:14 echo-area [~user@114.254.102.184] has joined #sbcl 01:18:31 SHUPFS [~user@S0106001111de1fc8.cg.shawcable.net] has joined #sbcl 01:49:24 -!- kanru [~kanru@2620:101:8003:200:8ea9:82ff:fe77:2e8e] has quit [Ping timeout: 240 seconds] 02:16:51 rbarraud [~rbarraud@222-155-139-54.jetstream.xtra.co.nz] has joined #sbcl 04:02:29 -!- Maroni [~user@94.245.247.183] has quit [Ping timeout: 260 seconds] 04:24:14 -!- echo-area [~user@114.254.102.184] has quit [Remote host closed the connection] 04:25:04 echo-area [~user@114.254.102.184] has joined #sbcl 05:06:37 slyrus [~chatzilla@adsl-99-190-99-176.dsl.pltn13.sbcglobal.net] has joined #sbcl 05:26:48 Are test failures in threads.pure.lisp on Mac OS 10.8 known? 05:26:52 (I received two) 05:27:31 (1.0.57) 05:32:30 which tests and do they fail on 10.7 as well? 05:34:14 Hm, I guess I have a vm running 10.7 05:35:27 RETURN-FROM-THREAD, NORMAL-THREAD 05:35:37 ABORT-THREAD NORMAL-THREAD 05:36:48 hmm... I don't have 10.8 yet, but hopefully will in the next few days. 05:37:28 I'm attempting with the latest SBCL sources now 05:40:45 slyrus, interesting. The latest source doesn't fail. 05:50:16 slyrus, I repeated .57 twice and the latest twice. Each was consistent; .57 failed on the aforementioned tests each time, the latest hasn't. 05:50:24 Not sure if I should file anything. 05:53:52 sdemarre [~serge@91.176.38.61] has joined #sbcl 06:14:02 kanru [~kanru@209.118.182.194] has joined #sbcl 06:24:11 -!- psilord [~psilord@c-69-180-173-249.hsd1.mn.comcast.net] has quit [Ping timeout: 272 seconds] 06:37:37 psilord [~psilord@c-69-180-173-249.hsd1.mn.comcast.net] has joined #sbcl 07:05:00 Maroni [~user@94.245.248.152] has joined #sbcl 07:40:19 dtw [~dtw@pdpc/supporter/active/dtw] has joined #sbcl 08:53:09 booklet [~booklet@unaffiliated/quadrescence] has joined #sbcl 08:56:29 -!- Maroni [~user@94.245.248.152] has quit [Ping timeout: 260 seconds] 08:58:57 how do sbcl devs feel about source code cleanup which doesnt strictly add/remove functionality or fix any bugs? 09:16:43 -!- wbooze [~wbooze@xdsl-78-35-155-2.netcologne.de] has quit [Ping timeout: 240 seconds] 09:48:24 -!- booklet [~booklet@unaffiliated/quadrescence] has quit [Quit: booklet] 10:52:39 chturne [~chturne@host86-148-233-236.range86-148.btcentralplus.com] has joined #sbcl 10:55:03 -!- dtw [~dtw@pdpc/supporter/active/dtw] has quit [Quit: ERC Version 5.3 (IRC client for Emacs)] 11:10:30 Quadrescence: not much has changed since then. did you build from .57 yourself or use a provided binary? 11:10:54 slyrus, I was building via 0.55 11:11:08 I used 0.55 to build both 0.57 and latest 11:13:36 OK, never mind then 11:46:20 minion: memo for booklet: it ought to be done, and I prefer it to happen in dedicated commits. 11:46:20 Remembered. I'll tell booklet when he/she/it next speaks. 11:46:36 minion: memo for booklet: (re source cleanups) 11:46:36 Remembered. I'll tell booklet when he/she/it next speaks. 11:57:29 pkhuong, that is me 11:58:29 pkhuong, what about stuff like single spelling errors? for some reason i have a feeling sbcl devs wouldn't like "fixed spelling error in a comment" as a commit 11:59:11 <|3b|> better than tacking it onto some unrelated change 11:59:14 batch them up! We have a great whitespacification commit too (: 11:59:40 Make sure you're conservative about those because I certainly don't feel like having people bikeshed over that commit. 12:03:20 antoszka: look for "[Sbcl-devel] RFC: exiting SBCL vs returning from a thread vs aborting a thread", on december 31st 2011. 12:05:50 pkhuong, "bikeshed"? 12:09:59 -!- sdemarre [~serge@91.176.38.61] has quit [Ping timeout: 272 seconds] 12:11:44 Quadrescence: bikeshed.com. 12:13:55 pkhuong, are you saying people should not care about what a commit is for, as long as it's understandable and improves the code? *or* do you mean something else 12:16:22 I just mean that I'd rather have the bandwidth on sbcl-devel used for other purposes than discussing the finer points of english grammar and how they may or may not apply to an internals comment. 12:18:23 pkhuong, oh, yeah, i agree with that. But as a result, are you saying "don't propose many spelling error commits" because that's not a good topic for discussion? 12:19:46 *|3b|* read it as "make sure any spelling/grammar commits are 100% obvious, because if anyone can argue them, they will" 12:20:49 hah, okay 12:21:43 that, and batch them in a single commit of orthographic doom so that it's easy to skip it when looking back in history. 12:23:36 yeah right 12:23:57 SBCL people would hate my commit habits. I take "commit early commit often" too seriously. :( 12:24:27 <|3b|> that works better for stuff that actually changes the behavior of the code 12:24:54 so do I, but I rewrite history afterward. Sometimes it's so bad that I just hack the diff directly instead of trying to reorder/merge/split commits just right. 12:25:08 sdemarre [~serge@91.176.80.96] has joined #sbcl 12:27:02 pkhuong, haha 12:27:51 I'm just writing source lines on my chalkboard that I see non-behavior-affecting things that are worth changing 12:33:53 _travis_ [~nonya@nc-71-52-232-124.dhcp.embarqhsd.net] has joined #sbcl 12:33:53 i've also been thinking about ways to refactor/improve srctran 12:36:49 I've been siding with Proebsting more and more now that I have an instance in which runtime ~doubles when the OS hands me unlucky physical addresses (: 12:48:43 -!- _travis_ [~nonya@nc-71-52-232-124.dhcp.embarqhsd.net] has quit [Ping timeout: 246 seconds] 13:07:39 pkhuong: Thx. 13:08:27 _travis_ [~nonya@nc-71-52-232-124.dhcp.embarqhsd.net] has joined #sbcl 13:12:52 -!- rbarraud [~rbarraud@222-155-139-54.jetstream.xtra.co.nz] has quit [Ping timeout: 246 seconds] 13:25:06 Maroni [~user@046-220-000-175.dyn.orange.at] has joined #sbcl 13:34:09 -!- Maroni [~user@046-220-000-175.dyn.orange.at] has quit [Ping timeout: 260 seconds] 14:01:52 -!- _travis_ [~nonya@nc-71-52-232-124.dhcp.embarqhsd.net] has quit [Ping timeout: 246 seconds] 14:25:06 wbooze [~wbooze@xdsl-78-35-150-240.netcologne.de] has joined #sbcl 14:30:12 -!- echo-area [~user@114.254.102.184] has quit [Read error: Connection reset by peer] 14:46:54 -!- Quadrescence [~quad@unaffiliated/quadrescence] has quit [Ping timeout: 264 seconds] 14:58:13 Quadrescence [~quad@unaffiliated/quadrescence] has joined #sbcl 15:26:00 -!- wbooze [~wbooze@xdsl-78-35-150-240.netcologne.de] has quit [Quit: Client Quit] 16:04:53 _travis_ [~nonya@nc-71-52-232-124.dhcp.embarqhsd.net] has joined #sbcl 16:08:15 -!- huangjs [~huangjs@190.8.100.83] has quit [Read error: Connection reset by peer] 16:08:59 -!- _travis_ [~nonya@nc-71-52-232-124.dhcp.embarqhsd.net] has quit [Ping timeout: 244 seconds] 16:11:52 _travis_ [~nonya@nc-71-52-232-124.dhcp.embarqhsd.net] has joined #sbcl 16:38:09 -!- _travis_ [~nonya@nc-71-52-232-124.dhcp.embarqhsd.net] has quit [Quit: Nettalk6 - www.ntalk.de] 16:55:37 wbooze [~wbooze@xdsl-78-35-150-240.netcologne.de] has joined #sbcl 16:59:46 -!- wbooze [~wbooze@xdsl-78-35-150-240.netcologne.de] has quit [Remote host closed the connection] 17:36:14 -!- antoszka [~antoszka@unaffiliated/antoszka] has quit [Ping timeout: 260 seconds] 17:40:11 attila_lendvai [~attila_le@37.99.60.86] has joined #sbcl 17:40:11 -!- attila_lendvai [~attila_le@37.99.60.86] has quit [Changing host] 17:40:11 attila_lendvai [~attila_le@unaffiliated/attila-lendvai/x-3126965] has joined #sbcl 17:43:28 antoszka [~antoszka@unaffiliated/antoszka] has joined #sbcl 18:01:50 -!- attila_lendvai [~attila_le@unaffiliated/attila-lendvai/x-3126965] has quit [Quit: Leaving.] 18:19:27 huangjs [~huangjs@190.8.100.83] has joined #sbcl 18:27:15 edgar-rft [~GOD@HSI-KBW-078-043-123-191.hsi4.kabel-badenwuerttemberg.de] has joined #sbcl 18:29:14 wbooze [~wbooze@xdsl-78-35-150-240.netcologne.de] has joined #sbcl 18:31:32 -!- wbooze [~wbooze@xdsl-78-35-150-240.netcologne.de] has quit [Client Quit] 18:34:57 wbooze [~wbooze@xdsl-78-35-150-240.netcologne.de] has joined #sbcl 18:56:09 -!- antoszka [~antoszka@unaffiliated/antoszka] has quit [Ping timeout: 260 seconds] 19:13:17 -!- ASau [~user@95-28-115-21.broadband.corbina.ru] has quit [Ping timeout: 252 seconds] 19:17:49 antoszka [~antoszka@unaffiliated/antoszka] has joined #sbcl 19:28:14 -!- antoszka [~antoszka@unaffiliated/antoszka] has quit [Ping timeout: 260 seconds] 19:35:37 antoszka [~antoszka@unaffiliated/antoszka] has joined #sbcl 19:41:40 -!- huangjs [~huangjs@190.8.100.83] has quit [Ping timeout: 246 seconds] 19:41:59 -!- antoszka [~antoszka@unaffiliated/antoszka] has quit [Ping timeout: 248 seconds] 19:48:59 huangjs [~huangjs@190.8.100.83] has joined #sbcl 19:49:15 -!- edgar-rft [~GOD@HSI-KBW-078-043-123-191.hsi4.kabel-badenwuerttemberg.de] has quit [Quit: unexpected death] 19:55:05 antoszka [~antoszka@unaffiliated/antoszka] has joined #sbcl 19:56:36 TimKack [~user@d115007.upc-d.chello.nl] has joined #sbcl 20:56:48 _travis_ [~nonya@nc-71-52-232-124.dhcp.embarqhsd.net] has joined #sbcl 20:59:16 ASau [~user@89-178-164-66.broadband.corbina.ru] has joined #sbcl 21:49:54 -!- sdemarre [~serge@91.176.80.96] has quit [Ping timeout: 264 seconds] 22:15:27 -!- _travis_ [~nonya@nc-71-52-232-124.dhcp.embarqhsd.net] has quit [Ping timeout: 272 seconds] 22:20:47 hargettp [~hargettp@pool-71-184-181-94.bstnma.east.verizon.net] has joined #sbcl 22:22:53 anyone else had any problems with Slime + SBCL x64 multi-threaded on Mac OS X Mountain Lion? After the OS ugprade this week, slime seems to freeze frequently 22:31:14 _travis_ [~nonya@nc-71-52-232-124.dhcp.embarqhsd.net] has joined #sbcl 22:44:31 -!- _travis_ [~nonya@nc-71-52-232-124.dhcp.embarqhsd.net] has quit [Ping timeout: 255 seconds] 22:44:56 _travis_ [~nonya@nc-71-52-232-124.dhcp.embarqhsd.net] has joined #sbcl 22:55:58 -!- _travis_ [~nonya@nc-71-52-232-124.dhcp.embarqhsd.net] has quit [Ping timeout: 252 seconds] 23:18:59 I haven't upgraded past 10.6 yet 23:19:29 10.7 was a nice upgrade; not sure about 10.8 yet...I think it is, but not sure 23:19:34 definitely incremental only 23:20:03 10.7 I thought did a better job of using multiple cores all the way around in the OS; 10.8 just seems like my Mac is turning into a handier iPhone 23:20:22 i don't use x64 anymore.... 23:20:27 only x86 23:20:37 does SBCL build on 10.8, while you're here? 23:20:47 I might just upgrade if it does 23:20:55 It runs, but I haven't built it. I should build it, just to see 23:21:12 and all of those binaries should just detect 64bit capab and do it the 64bit way if necessary in my opinion, having to divert everything into either one or the other is a mess...... 23:21:13 heck, let's get that going...I have a labeled 1.0.57 already... 23:21:50 if if someone has multilib gcc...... 23:21:53 even* 23:24:05 pkhuong: getting gcc on Mac is a bit different than a few revs back; used to come with XCode (IIRC), but then in 10.7 they broke it out separately. I still get it as an extra download with XCode, but I think it can be installed separately without XCode 23:26:43 fyi - SBCL 1.0.57 x64 build now going on 10.8 Mac OS X Mountain Lion 23:26:52 oy, the heat of my laptop burned my leg... ;) 23:29:03 -!- wbooze [~wbooze@xdsl-78-35-150-240.netcologne.de] has quit [Quit: Client Quit] 23:30:06 wbooze [~wbooze@xdsl-78-35-150-240.netcologne.de] has joined #sbcl 23:32:28 [18:20.38] does SBCL build on 10.8, while you're here? // the latest does 23:32:37 did you see my comments about building .57 and the latest? 23:33:17 don't think so 23:37:01 pkhuong: huh, not 100% comforting...slightly different behavior the first time I built from the 2nd time... 23:37:37 pkhuong: you know how normally the build ends with instructions to run "sh install.sh?" First time I build, that did not happen (pretty sure I ran clean.sh first); 2nd time it did 23:38:30 pkhuong: uh oh, and I did disable multi-threading in that 2nd build...which explains why the first time the sb-concurrency contrib had problems, but not the second time 23:40:54 ugh...I wonder if its similar to this issue with slime autodoc already reported against Slime: https://bugs.launchpad.net/slime/+bug/1012811 23:44:05 oy, so that's it: building with threading disabled on 10.8 x64 seems fine, with threading enabled...build doesn't finish (complains about contribu sb-concurrency) 23:44:12 I'm building again to verify that's true 23:47:48 -!- TimKack [~user@d115007.upc-d.chello.nl] has quit [Remote host closed the connection] 23:54:42 -!- wbooze [~wbooze@xdsl-78-35-150-240.netcologne.de] has quit [Ping timeout: 264 seconds] 23:58:21 -!- Phoodus [~foo@ip72-223-116-248.ph.ph.cox.net] has quit [Ping timeout: 255 seconds] 23:59:46 pkhuong: yep, so i think it's related to the same underlying issue that was previously reported...that was on a pre-release of Mountain Lion, I have the official release version, and simpilar issue. It's this bug https://bugs.launchpad.net/sbcl/+bug/1012811 23:59:59 I added some more info to the bug, just in case