00:00:00 --- log: started forth/19.08.05 00:06:05 --- join: xek (~xek@apn-31-0-23-83.dynamic.gprs.plus.pl) joined #forth 00:18:47 --- join: dys (~dys@2003:5b:203b:100:a64c:c8ff:fef4:13a6) joined #forth 00:28:58 --- quit: xek (Ping timeout: 272 seconds) 00:32:55 --- quit: deesix (Ping timeout: 245 seconds) 03:39:21 --- join: dddddd (~dddddd@unaffiliated/dddddd) joined #forth 03:43:56 --- join: deesix (~dddddd@unaffiliated/dddddd) joined #forth 04:50:43 --- join: dave0 (~dave0@069.d.003.ncl.iprimus.net.au) joined #forth 05:21:52 --- join: C-Keen (cckeen@k4cg/C-Keen) joined #forth 05:29:36 rdrop-exit, thanks. that is what colorforth does, correct? 05:44:56 remexre, native threading is not always possible - on some systems you can not make code space both writeable and executable for security reasons and in that case you have no option other than to use indirect threading 05:45:11 a good example is the android system im developing a forth for (again) 05:45:27 but i dont have time to stop and chat, im omw to work :) 05:45:31 --- quit: mark4 (Quit: bbl) 05:48:22 --- join: ryke (~Thunderbi@71-9-169-152.dhcp.jcsn.tn.charter.com) joined #forth 05:51:35 that's a nice feature for indirect threading 05:58:28 i read this paper on indirect/direct hybrid threading but i didn't get it: https://pdfs.semanticscholar.org/b520/19469cbce6630b39a0a6743975219e795a3f.pdf 05:58:51 it confused me 06:01:56 it's not a huge deal of writing and then executing code imho because there's a few high profile programs that use it: java's JIT, qemu and other emulators also with JIT 06:23:00 --- quit: ryke (Ping timeout: 272 seconds) 06:37:47 --- join: nonlinear (znc@tilde.team) joined #forth 06:38:11 --- nick: nonlinear -> Guest53381 06:38:37 --- quit: Guest20459 (Read error: Connection reset by peer) 09:25:46 --- quit: Keshl (Read error: Connection reset by peer) 09:26:01 --- join: Keshl (~Purple@207.44.70.214.res-cmts.gld.ptd.net) joined #forth 09:41:15 --- quit: Keshl (Read error: Connection reset by peer) 09:41:34 --- join: Keshl (~Purple@207.44.70.214.res-cmts.gld.ptd.net) joined #forth 09:48:46 --- quit: dave0 (Quit: dave's not here) 10:44:21 huh, TIL about this https://excamera.com/sphinx/docforth.html 10:44:41 the resulting doc page looks nice, https://excamera.com/files/docforth/docforth/mt19937.txt.html 10:49:42 --- join: ryke (~Thunderbi@71-9-169-152.dhcp.jcsn.tn.charter.com) joined #forth 11:00:19 --- quit: dys (Ping timeout: 250 seconds) 11:06:44 --- quit: bluekelp (Ping timeout: 268 seconds) 11:07:10 --- join: bluekelp (~pp@bluekelp.com) joined #forth 11:15:55 --- join: wildtrees (~wildtrees@unaffiliated/wildtrees) joined #forth 11:49:17 --- join: dys (~dys@tmo-112-123.customers.d1-online.com) joined #forth 12:40:28 --- quit: gravicappa (Ping timeout: 272 seconds) 13:11:30 --- quit: john_metcalf (Ping timeout: 272 seconds) 13:23:19 --- quit: dys (Ping timeout: 245 seconds) 13:27:07 --- join: dys (~dys@tmo-105-177.customers.d1-online.com) joined #forth 14:07:30 --- quit: ryke (Ping timeout: 245 seconds) 15:28:19 --- quit: X-Scale (Ping timeout: 245 seconds) 16:25:44 --- join: dave0 (~dave0@069.d.003.ncl.iprimus.net.au) joined #forth 16:40:01 --- quit: john_cephalopoda (Ping timeout: 264 seconds) 16:52:48 --- join: john_cephalopoda (~john@unaffiliated/john-cephalopoda/x-6407167) joined #forth 16:56:10 --- quit: wildtrees (Quit: Leaving) 17:39:24 --- join: tabemann (~tabemann@rrcs-162-155-170-75.central.biz.rr.com) joined #forth 18:02:09 --- quit: tabemann (Read error: Connection reset by peer) 18:03:26 --- join: tabemann (~tabemann@rrcs-162-155-170-75.central.biz.rr.com) joined #forth 18:03:46 --- quit: tabemann (Remote host closed the connection) 19:04:29 dave0: what's a nice feature? the not-needing-writable-and-executable memory? 19:05:25 and if the OS enforces W^X and doesn't have mmap, it's plausible said JIT would be impossible tho 19:06:41 though to my knowledge, Android has mmap, so one should be able to just do mmap(NULL, 4096, PROT_EXEC|PROT_READ|PROT_WRITE, MAP_ANONYMOUS, -1, 0) and get a writable, executable page 19:06:56 idk if mark4's using JNI though 19:26:38 --- join: X-Scale (~ARM@92.250.101.35) joined #forth 19:30:00 --- join: tabemann (~tabemann@2600:1700:7990:24e0:3c20:f40:6e45:c0be) joined #forth 20:18:23 separate but kinda related question: are there any particularly good approaches to profiling Forth? I'm currently considering doing it via the serial port, by firing an interrupt that sends back the instruction pointer and return stack, and running this from a second machine every few ms 20:18:43 Was wondering if there's a nice approach to interleave it into "codegen," though 20:40:30 --- quit: dddddd (Remote host closed the connection) 21:01:27 --- join: gravicappa (~gravicapp@h109-187-199-149.dyn.bashtel.ru) joined #forth 21:07:58 --- join: karswell (~user@cust125-dsl91-135-5.idnet.net) joined #forth 21:09:48 --- quit: karswell (Remote host closed the connection) 21:11:13 --- join: karswell (~user@cust125-dsl91-135-5.idnet.net) joined #forth 21:13:18 --- quit: karswell (Remote host closed the connection) 21:14:43 --- join: karswell (~user@cust125-dsl91-135-5.idnet.net) joined #forth 22:08:12 --- quit: louisg (Ping timeout: 258 seconds) 22:11:08 --- join: louisg (~louis@x-160-94-179-187.acm.umn.edu) joined #forth 23:01:15 --- quit: MrMobius (Ping timeout: 245 seconds) 23:12:32 --- quit: dave0 (Quit: dave's not here) 23:31:25 --- join: MrMobius (~default@c-73-134-82-217.hsd1.va.comcast.net) joined #forth 23:53:14 --- quit: tp (Read error: Connection reset by peer) 23:59:59 --- log: ended forth/19.08.05