00:00:00 --- log: started forth/19.08.04 00:15:42 --- quit: chunkypuffs (Remote host closed the connection) 00:18:54 --- join: chunkypuffs (~chunkypuf@static.203.112.216.95.clients.your-server.de) joined #forth 02:54:43 --- quit: dys (Ping timeout: 268 seconds) 03:00:51 --- join: dys (~dys@tmo-103-103.customers.d1-online.com) joined #forth 03:10:08 --- quit: dys (Ping timeout: 268 seconds) 03:21:48 --- join: dddddd (~dddddd@unaffiliated/dddddd) joined #forth 03:31:16 --- join: dys (~dys@tmo-119-166.customers.d1-online.com) joined #forth 06:27:58 found this by complete accident http://codepad.org/l23auJxo 06:28:13 not forth, but i thought it was cool 06:33:23 * CORDIC : 06:45:23 loled 06:50:42 apparently it does keep going too 06:50:59 *0x1p52 produces 123456789ab 08:53:06 --- quit: proteusguy (Ping timeout: 244 seconds) 08:57:22 --- join: proteusguy (~proteusgu@cm-58-10-208-146.revip7.asianet.co.th) joined #forth 08:57:22 --- mode: ChanServ set +v proteusguy 10:23:10 --- join: ryke (~Thunderbi@71-9-169-152.dhcp.jcsn.tn.charter.com) joined #forth 10:35:52 --- quit: Keshl (Read error: Connection reset by peer) 10:36:11 --- join: Keshl (~Purple@207.44.70.214.res-cmts.gld.ptd.net) joined #forth 11:35:05 --- quit: ryke (Ping timeout: 248 seconds) 12:35:24 --- join: mark4 (~mark4@rrcs-67-79-14-26.sw.biz.rr.com) joined #forth 12:35:55 has any actual project used up more than 0xffffffff of code/data space (i.e. resident in memory at same time) 12:37:04 im porting t4 to 64 bit arm for android ndk which means i have to be indirect threaded... having 64 bit xt's seems pretty damned wasteful and probably not a good idea. im thinking of limiting the forth to 32 bits of address space but allowing 64 bit numerical calculations 12:41:14 --- join: gravicappa (~gravicapp@h109-187-63-35.dyn.bashtel.ru) joined #forth 12:47:30 --- quit: gravicappa (Ping timeout: 245 seconds) 13:28:33 --- quit: tabemann (Ping timeout: 250 seconds) 13:29:20 --- quit: reepca (Read error: Connection reset by peer) 13:29:54 --- join: reepca (~user@208.89.170.37) joined #forth 13:41:48 --- join: tabemann (~tabemann@71-13-2-250.static.ftbg.wi.charter.com) joined #forth 13:58:32 --- quit: tabemann (Remote host closed the connection) 14:10:06 --- join: mycroftiv (~glen@45.76.231.16) joined #forth 14:15:00 23:09:44 JOIN (mycroftiv) 14:17:52 --- join: xek (~xek@apn-31-0-23-83.dynamic.gprs.plus.pl) joined #forth 14:22:05 --- quit: xek (Read error: Connection reset by peer) 14:24:48 --- join: tabemann (~tabemann@71-13-2-250.static.ftbg.wi.charter.com) joined #forth 14:25:19 --- join: ashirase (~ashirase@modemcable098.166-22-96.mc.videotron.ca) joined #forth 14:49:27 --- join: ryke (~Thunderbi@71-9-169-152.dhcp.jcsn.tn.charter.com) joined #forth 14:50:37 --- quit: ryke (Client Quit) 14:50:50 --- join: ryke (~Thunderbi@71-9-169-152.dhcp.jcsn.tn.charter.com) joined #forth 14:51:54 --- quit: tabemann (Ping timeout: 268 seconds) 15:02:23 --- join: tabemann (~tabemann@2600:1700:7990:24e0:79a7:6cf:31f6:4dfc) joined #forth 15:26:50 --- quit: dys (Ping timeout: 246 seconds) 15:49:27 --- quit: mark4 (Remote host closed the connection) 15:49:40 --- join: mark4 (~mark4@rrcs-67-79-14-26.sw.biz.rr.com) joined #forth 16:10:01 --- quit: proteusguy (Remote host closed the connection) 16:37:55 --- quit: tabemann (Ping timeout: 250 seconds) 16:40:05 --- quit: john_cephalopoda (Ping timeout: 250 seconds) 16:40:37 --- join: X-Scale (~ARM@83.223.241.59) joined #forth 16:53:34 --- join: john_cephalopoda (~john@unaffiliated/john-cephalopoda/x-6407167) joined #forth 17:10:08 --- quit: reepca (Ping timeout: 244 seconds) 17:14:51 if i do : foo xxx yyy zzz .... ; and zzz does not exist should that backtrack the compilation up to that point so dictionary space is not wasted? 17:15:07 i dont actually do that in any of my current forths, not sure if anyone does anywhere else 17:15:14 --- join: tabemann (~tabemann@rrcs-162-155-170-75.central.biz.rr.com) joined #forth 17:44:15 I do not backtrack in my systems 17:44:35 im not even sure if anyone does :) 17:44:40 you can always empty 17:50:14 --- quit: ashirase (Quit: ZNC - http://znc.in) 18:24:10 --- quit: ryke (Ping timeout: 245 seconds) 18:32:54 --- join: ryke (~Thunderbi@71-9-169-152.dhcp.jcsn.tn.charter.com) joined #forth 18:38:22 zForth has backtracing https://github.com/zevv/zForth 18:43:25 o/ mycroftiv! I remember you from the 9fans mailing list. 18:45:48 http://9gridchan.org/ 18:56:32 --- quit: tabemann (Read error: Connection reset by peer) 18:57:38 --- join: tabemann (~tabemann@rrcs-162-155-170-75.central.biz.rr.com) joined #forth 18:58:21 --- quit: tabemann (Remote host closed the connection) 19:04:51 --- join: rdrop-exit (~markwilli@112.201.162.86) joined #forth 19:22:20 --- join: reepca (~user@208.89.170.37) joined #forth 19:54:05 --- join: dave0 (~dave0@069.d.003.ncl.iprimus.net.au) joined #forth 21:20:42 --- quit: reepca (Remote host closed the connection) 21:25:11 --- join: dys (~dys@tmo-103-90.customers.d1-online.com) joined #forth 21:25:19 pointfree: yeah thats me, currently im buried in learning forth in pforth in plan 9 21:25:29 --- quit: ryke (Ping timeout: 248 seconds) 21:26:31 --- join: gravicappa (~gravicapp@h109-187-63-35.dyn.bashtel.ru) joined #forth 21:44:41 --- quit: mark4 (Read error: Connection reset by peer) 21:45:35 --- join: mark4 (~mark4@rrcs-67-79-14-26.sw.biz.rr.com) joined #forth 21:46:21 --- quit: dddddd (Remote host closed the connection) 21:48:08 mycroftiv: cool, you are into forth too. 21:48:26 I am thinking of writing the pforth interpreter for amd64 6a native. 21:48:33 I am still exploring how to do that. 21:48:55 A decade ago, I had written a half assed forth interpreter on avr. 21:48:59 --- join: dave69 (~dave0@069.d.003.ncl.iprimus.net.au) joined #forth 21:49:56 I am thinking of using colorforth like call/jmp's instead of reading a forth word and call'ing or jmp'ing to it. 21:50:00 --- quit: dave0 (Ping timeout: 245 seconds) 21:50:31 not pforth, but, a dialect of forth. 21:52:18 --- nick: dave69 -> dave0 21:59:11 --- join: reepca (~user@208.89.170.37) joined #forth 22:07:24 --- quit: dave0 (Quit: dave's not here) 22:27:22 joe9, Subroutine Threaded Code (SRT), with the possibility of Native Code Inlining (SRT/NCI) 22:28:44 That would be the threaded code variant where you lay down calls to the words, and sometimes directly inline a word 22:30:02 Some use the abbreviation STC instead of SRT 22:32:13 The native code can be for a real machine or a virtual machine as the case may be 22:37:04 An optional next step, once you add NCI a peephole optimizer 22:37:31 * ... NCI is a ... 23:12:36 --- quit: rdrop-exit (Quit: Lost terminal) 23:17:53 smth I've been meaning to figure out -- STC is gobs faster than DTC/ITC on modern amd64, right? 23:18:27 (and it is because the CPU knows how to predict a ret, but not an e.g. lodsq; jmp rax) 23:57:18 --- quit: dys (Ping timeout: 272 seconds) 23:59:59 --- log: ended forth/19.08.04