00:00:00 --- log: started forth/05.09.10 00:50:40 --- join: amca (n=plump@as-bri-3-221.ozonline.com.au) joined #forth 00:51:05 Evening 00:55:32 --- quit: amca (Remote closed the connection) 01:00:47 --- join: amca (n=plump@as-bri-4-1-40.ozonline.com.au) joined #forth 02:40:11 --- join: aum (n=aum@60-234-156-82.bitstream.orcon.net.nz) joined #forth 03:37:38 --- quit: amca ("d34d") 05:04:35 --- join: PoppaVic (n=pete@0-1pool75-219.nas24.chicago4.il.us.da.qwest.net) joined #forth 05:06:09 Howdy 05:08:58 --- join: h722 (n=h722@82.52.55.134) joined #forth 05:09:02 hi 05:09:50 anyone here? 05:09:56 yah 05:10:02 oh, hy PoppaVic 05:11:49 may I ask you "assistance" about English? :)))) 05:11:58 huh? 05:12:05 i am italian :( 05:12:15 it's not your fault, really. 05:12:21 :P 05:13:05 I have 14 lines written in english 05:13:22 OK, but this is #forth 05:13:38 yeah 05:13:50 may you suggest 05:13:57 a chan where to ask ? 05:14:13 no idea. I have no idea what you want, either. 05:14:27 just a check of grammar :) 05:14:48 and thank you really much anyway 05:14:52 just show me a paste-shight url 05:15:00 sight (sheesh) 05:15:05 k 05:15:24 pvt or here? 05:15:35 here is fine, just a short url, no? 05:15:50 k i am going to put it in an url 05:20:54 i think i'm stupid :( 05:21:03 sorry for being late 05:21:35 http://www-dimat.unipv.it/~arico/acknowledgments.txt 05:22:13 it's because the advisor checked all the file, but not this page of course ;) 05:22:57 --- nick: h722 -> antaro 05:27:23 "I had been to Pav..." 05:27:44 I knew nothing about..." 05:27:55 :))))))))) 05:27:58 tnx 05:28:15 "years, during which..." 05:28:37 "of meeting" 05:28:51 "whom is also" 05:29:16 "one of the kindest men" 05:29:31 "helpful" 05:30:04 "special thanks" ... "been very friendly" 05:30:27 "who taught" 05:30:29 fantastic 05:30:43 that sounds really goot tnx tnx 05:30:46 "useful" (again) 05:31:18 I think does it all, you will want to read it aloud to yourself after all the fixes. 05:32:45 oh, yes 05:33:05 maybe I should thank also you :) 05:33:16 anyway, tnx really really much 05:33:26 :)))))))))) 05:34:00 [and, if a math. can help you, you know where to find it also by mail :) ] 05:34:11 hmm? 05:34:12 --- join: Topaz (n=top@spc1-horn1-6-0-cust128.cosh.broadband.ntl.com) joined #forth 05:34:25 good luck. 05:34:30 tnx 06:04:44 hmph hmph... relative-addresses... 06:10:58 I hate those "blast from the dark" wild-thoughts that snap in on yah. 06:16:47 I've just managed to envision an 'issue' early-on and I'm trying to resolve its "headspace". There are an awful lot of absolute-address ops/use, aren't there? 06:21:23 --- join: tathi (n=josh@pdpc/supporter/bronze/tathi) joined #forth 06:21:23 hi tathi 06:21:23 I just started a new line of query above 06:24:24 hmm.. Lotsa' lag 06:26:06 tathi: here's my brainfart... We sure seem to suffer an awful lot of absolute-address memory access. Seems like it's damn near fundamental. 06:28:21 I don't really mind working from absolutes on stacks. But, it seems more than likely they'd tend to get embedded as well. 06:29:35 This seems to sorta' suggest that the decompiler/cross-compiler ideas would become a typical bitch. 06:31:45 Unless the silly things would require a sourcefile, instead of use images? Hell, even saving/loadingimages suffers if we have absolute-addresses. 06:32:29 hmm 06:37:05 yup. 06:37:43 Can you see a rel-addr alternative to the mess? I'm tinkering with a few theories, but so far to no conclusion. 06:39:27 oh.. heh.. hmmm... maybe..... 06:39:56 not really... 06:40:12 I'm just using all addresses as offsets from the base of the memory. 06:40:54 i.e. all addresses are relative to the start of the image. 06:41:05 or can think of it as absolute addresses starting at 0. 06:41:06 yeah. 06:41:18 I was thinking of that, or a ptr-stack 06:41:54 ..now.. What happens when we interface with malloc/free? use our own code and form a LL, is my guess. 06:42:02 of course, if you're planning on dealing with addresses outside of your image block, what I'm doing won't work. 06:42:10 assuredly 06:42:47 it also can bollix if we save an image with certain size-expectations and load that image into a new, increased space 06:43:16 how so? 06:43:31 I can see you would have problems if you decreased the space, but problems on increasing? 06:43:59 I'm thinking of image[....PLUS stackspaces/uservar] - I think it COULD get stupid fast 06:44:26 ah. 06:44:37 unless.. hmm.. 06:44:44 yeah, I wasn't planning on allowing access into the stackspaces by address. 06:45:00 Mine was somewhat planned to help migration to custom hardware at some point. 06:45:15 well, you can't hardly stop them when they have keywords to help them, of course 06:46:18 ok, let's make an assumption of thus: UP0[........]Image[........] { stacks } 06:46:56 if they tick or do assorted tick @, and then embed it. Are they not gonna' skullfuck us? 06:48:39 I can already see that the best way to handle uvar is to return an offset, and embed literal-handlers and offsets. But, forth allows so much up/down language-scale capability, it might all be moot. 06:49:27 given ticks/fetches and such and , - they can quickly ruin the day 06:50:33 unless we can voodoo between "compiling" and "interpreting" or some other freaky mix 06:51:11 I'm tempted to suggest a pointer-stack 06:52:26 and, given THAT, I recall some discussions I had before of a stack paralleling the data-stack which just marked things as values/pointers. 06:52:39 or "handler stack" 06:53:32 interestingly, I think that "handler-stack" is only of interest to the interpreter/compiling-words 07:07:12 ANyway, thought I'd share the issue/ideas and see what it lead to. 07:12:13 --- quit: onetom (Read error: 104 (Connection reset by peer)) 07:16:07 --- join: onetom (n=tom@ns.dunasoft.com) joined #forth 07:32:19 --- quit: aum () 07:49:42 byez 07:49:52 and thank you :))) 07:50:26 --- quit: antaro ("Client Exiting") 07:57:47 humph-humph.. *sigh* I think I'm seeing new patterns. 08:37:14 brb 08:37:19 --- quit: PoppaVic ("Pulls the pin...") 08:41:19 --- join: PoppaVic (n=pete@0-1pool73-128.nas24.chicago4.il.us.da.qwest.net) joined #forth 08:41:36 damned isp 09:03:29 --- quit: Topaz ("Leaving") 09:10:52 moo 09:11:36 gah 09:16:02 moo, yourself :) 09:19:35 gad this is a sucky slut 09:27:07 Failed to open /DEV/Metabuilder/fovm/structs/h for reading: No such file or directory 09:27:20 http://rafb.net/paste/results/LxjiZD43.html 09:27:36 damnnit... Look at eof and ihead, tathi 09:28:27 I've decided to examine top-down and bottom-up and see if I can reconcile addresses/sizes 09:31:59 To be honest.. I'm not sure how a mmap compares to malloc, but I'm willing to CONSIDER differences. 09:44:22 * PoppaVic sighs 09:44:33 good day to y'all 09:44:35 --- quit: PoppaVic ("Pulls the pin...") 10:12:36 --- join: PoppaVic (n=pete@0-1pool47-129.nas30.chicago4.il.us.da.qwest.net) joined #forth 10:26:23 hi everyone 10:27:54 lo, crc 10:28:39 if you can tail back, I wish you would: I'm about ready for a nap 10:29:07 ok, I'll be here for several hours at least :) 10:29:19 * crc reads the backlog now... 10:39:30 --- join: Topaz (n=top@spc1-horn1-6-0-cust128.cosh.broadband.ntl.com) joined #forth 10:41:30 crc: anyway, I'm tuckered.. The issues are as obtuse in ##C and #forth lately - and forget #asm. I'll talk to you tomorrow. I've gotten too tired and lost interest today. 10:41:33 --- quit: PoppaVic ("Pulls the pin...") 12:32:11 --- quit: derv0 (Read error: 110 (Connection timed out)) 12:33:41 --- join: derv0 (n=derv0@proxy1.nscl.msu.edu) joined #forth 13:50:25 --- quit: Topaz (Read error: 110 (Connection timed out)) 14:03:40 --- join: Topaz (n=top@spc1-horn1-6-0-cust128.cosh.broadband.ntl.com) joined #forth 14:04:01 --- quit: Topaz (Client Quit) 14:04:07 --- join: Topaz (n=top@spc1-horn1-6-0-cust128.cosh.broadband.ntl.com) joined #forth 14:21:31 --- join: JasonWoof (n=jason@c-24-218-59-196.hsd1.ma.comcast.net) joined #forth 14:21:32 --- mode: ChanServ set +o JasonWoof 14:28:43 Hey, JasonWoof. 14:29:59 --- quit: Topaz (Read error: 104 (Connection reset by peer)) 15:31:57 hi Quartus :) 15:32:33 just moved a bunch of stuff around in the garage to make more room for bikes 15:32:53 now hopefully I won't have to park people in so much 15:47:10 Good deal. 15:47:53 ahhh 15:47:55 then a shower 15:48:27 hmmm 15:48:38 there's game night at the comic shop in 25 minutes 15:49:23 oh, the other good news ;) 15:49:31 I made $8.75 at our tag sale today 15:49:53 and I got rid of a bunch of stuff :) 15:52:56 i got the raytracer to run in 30 seconds, -vs- 40 yesterday 15:56:16 cool 15:56:34 you improving your raytracing code? or factor? 15:56:44 can I see the image it generates? 15:57:14 i'm improving the factor compiler 15:57:27 the algorithm is quite naive 15:57:28 http://factor.sourceforge.net/raytracer.png 15:57:48 cool 15:58:44 it runs 12.5 times slower than the C++ version on my computer 15:59:17 not too bad 15:59:20 the java version is about 3 times faster than the C++, surprisingly enough 15:59:26 even though they both use the same algorithm 15:59:31 very weird 15:59:37 g++ sucks i guess 15:59:45 i'm compiling with -O3 -ffast-math -fomit-frame-pointer 15:59:50 you passing the optomizing fl 15:59:52 wow 15:59:55 that's really strange 15:59:56 and java with -server -Xbatch 16:00:17 does it do a function call each iteration? 16:00:25 it does tons of function calls on each iteration 16:00:32 oh sorry 16:00:34 it uses objects to represent 3-vectors 16:00:36 I'm thinking mandelbrot 16:01:16 function call overhead is considerable in C 16:02:38 you generating machine code in factor? 16:02:46 yes 16:05:06 i need to make better use of registers, and infer more types 16:05:35 I wonder what sort of overhead fovium has 16:05:57 maybe I'll code that rediculous recursive fibinocci 16:06:59 factor does recursive fib several times faster than gforth 16:11:51 cool 16:34:04 --- join: aum (n=aum@60-234-156-82.bitstream.orcon.net.nz) joined #forth 16:35:09 hmm... that took a while 16:35:54 I got ?if wrong, and < was buggy in the vm implementation 16:36:50 hmm... maybe if I go downstairs there will be food 16:59:53 --- quit: tathi ("leaving") 18:04:16 --- quit: crc (Read error: 110 (Connection timed out)) 18:19:22 --- join: crc (i=crc@pool-70-110-210-74.phil.east.verizon.net) joined #forth 18:56:13 --- join: Pepe_Le_Pew (n=User@201008249014.user.veloxzone.com.br) joined #forth 19:41:01 --- join: saon_ (i=1000@c-24-129-89-116.hsd1.fl.comcast.net) joined #forth 19:55:32 --- join: snoopy_16 (i=snoopy_1@dsl-084-058-142-115.arcor-ip.net) joined #forth 19:58:56 --- quit: crc (Read error: 110 (Connection timed out)) 20:02:33 --- quit: JasonWoof ("dude man") 20:10:10 --- quit: Pepe_Le_Pew ("Fui embora") 20:13:12 --- quit: Snoopy42 (Read error: 110 (Connection timed out)) 20:13:28 --- nick: snoopy_16 -> Snoopy42 20:51:53 --- quit: aum () 23:24:58 --- quit: madwork (Read error: 110 (Connection timed out)) 23:59:59 --- log: ended forth/05.09.10