00:00:00 --- log: started forth/17.11.02 01:43:18 --- join: mtsd (~mtsd@c83-254-190-39.bredband.comhem.se) joined #forth 02:07:48 --- quit: nighty-__ (Ping timeout: 246 seconds) 02:08:03 --- join: nighty-_ (~cp@s229123.ppp.asahi-net.or.jp) joined #forth 02:27:51 --- quit: dys (Ping timeout: 248 seconds) 02:52:57 --- join: dys (~dys@tmo-098-240.customers.d1-online.com) joined #forth 03:31:24 --- join: ncv (~neceve@unaffiliated/neceve) joined #forth 03:33:10 --- quit: mtsd (Remote host closed the connection) 03:34:30 --- quit: proteusguy (Remote host closed the connection) 04:02:30 --- join: proteusguy (~proteus-g@2405:9800:bc10:1ca:2c95:8326:4a4d:5097) joined #forth 04:02:30 --- mode: ChanServ set +v proteusguy 05:06:06 --- join: mtsd (~mtsd@c193-150-231-183.bredband.comhem.se) joined #forth 05:29:15 --- quit: nighty-- (Quit: Disappears in a puff of smoke) 05:30:45 --- quit: ncv (Ping timeout: 255 seconds) 07:05:22 am I losing my mind or is itc considerably faster than dtc on x86 07:06:45 the only way I can get dtc to be faster (and only marginally so) is if the interpreters are inlined into the code field, so no call or jmp, and that just sounds like it's going to be nasty to deal with down the road 07:38:03 I wish I had more time to spend on this stuff. I'm starting to feel like john[lisbeth], just burning rubber and not actually doing anything 08:14:49 --- quit: impomatic (Ping timeout: 240 seconds) 08:18:05 --- join: impomatic (~impomatic@host109-149-159-124.range109-149.btcentralplus.com) joined #forth 08:51:35 --- quit: mtsd (Remote host closed the connection) 09:08:35 --- mode: crc set +o koisoke 10:32:36 --- quit: proteusguy (Ping timeout: 252 seconds) 10:58:46 The only way to know for sure is to measure. So you're donig the right thing. 10:59:18 Maybe it's something about sharing code and data in the same cache lines. 11:00:11 I think it's just that two memory fetches and one jump is better than one memory fetch and a jump and then a call 11:01:34 Right, it could be many things. I'm not going to speculate too much. 11:02:48 tbh it's actually a relief, because I'm much more comfortable working with itc. if it had turned out that dtc was like twice as fast, I'd have a moral dilemma on my hands 11:05:16 I made my first Forth ITC. It's not the fastest option, but it's still plenty fast for my applications (which is mostly rebuilding itself). 11:05:44 No need to agonize over performance unless it's actually hurting somewhere. 11:06:10 yeah, I know I'm over-and-prematurely optimizing 11:06:13 I just can't help myself 11:06:50 well, I shouldn't say that. I can help myself, I just kept wondering about this specifically and wanted to satisfy the curiousity 11:12:08 --- quit: impomatic (Ping timeout: 264 seconds) 11:12:50 --- join: impomatic (~impomatic@host109-149-159-240.range109-149.btcentralplus.com) joined #forth 11:13:30 --- join: ncv (~neceve@2a02:c7d:c5c9:a900:c792:a3e8:397d:b37) joined #forth 11:13:30 --- quit: ncv (Changing host) 11:13:30 --- join: ncv (~neceve@unaffiliated/neceve) joined #forth 11:45:44 --- join: proteusguy (~proteus-g@2405:9800:bc10:1ca:2c95:8326:4a4d:5097) joined #forth 11:45:44 --- mode: ChanServ set +v proteusguy 12:03:23 --- quit: impomatic (Ping timeout: 240 seconds) 14:32:41 --- quit: mnemnion (Remote host closed the connection) 14:32:50 --- quit: ncv (Ping timeout: 240 seconds) 14:51:19 --- quit: dys (Ping timeout: 248 seconds) 16:24:53 --- join: Gromboli (~Gromboli@static-72-88-80-103.bflony.fios.verizon.net) joined #forth 17:51:30 --- quit: MrBusiness (Ping timeout: 252 seconds) 17:51:47 --- join: MrBismuth (~ArcMrBism@2602:306:8325:a300:3cd4:aa5a:1eb7:eb6f) joined #forth 19:39:56 Anyone have any suggestions for a forth that can run as the OS on an ARM system? 19:40:07 ARMv7, specificially (I think) 20:14:25 ZombieChicken: mecrisp seems to be popular 20:15:24 ZombieChicken: an arm variant of eForth is floating around if you want to take your crack at understanding completely how such system works. 20:22:09 ty 21:25:36 --- quit: Gromboli (Quit: Leaving) 23:59:59 --- log: ended forth/17.11.02