00:00:00 --- log: started forth/20.04.04 00:01:00 --- join: Zarutian_HTC joined #forth 00:59:56 --- join: john_cephalopoda joined #forth 01:01:22 Hey 01:33:12 --- join: xek__ joined #forth 02:13:05 --- join: `presiden joined #forth 02:27:21 --- quit: john_cephalopoda (Remote host closed the connection) 02:27:34 --- join: john_cephalopoda joined #forth 02:35:09 hey 02:37:36 <`presiden> ...listen 02:39:32 --- quit: xek__ (Ping timeout: 256 seconds) 02:43:03 Hey webchat9 02:43:15 Also hi `presiden. 02:43:39 Greetings everyone. 02:43:54 When will I be able to IRC from Your Forth john_cephalopoda ? 02:44:06 <`presiden> greetings 02:45:06 DKordic: I don't have my own Forth. I am doing a lot of stuff with crc's RETRO Forth though. And there's an IRC bot for that in the official examples ;) 02:47:01 OK I am looking for a BareMetal Forth implementation. 02:50:21 tabemann, latest commit is drawing full power, is low power disabled ? 02:58:44 --- join: WilhelmVonWeiner joined #forth 03:01:39 DKordic: RETRO runs on bare-metal x86. 03:03:09 And I wrote an assembler in RETRO, so you can eventually bootstrap RETRO on bare-metal x86. 03:04:09 john_cephalopoda, doesn't retro normally run under an OS, I have it running on FreeBSD here ? 03:04:35 It does, but it also includes C sources that allow you to run it on x86 natively. 03:05:37 ahh 03:38:25 https://cuttle.space/tmp/kernel-x86 03:38:37 --- quit: tabemann (Ping timeout: 252 seconds) 03:38:42 --- join: tabemann_ joined #forth 03:38:51 It's a mandelbrot thingie in RETRO running on plain x86. 03:39:15 (A little broken because it writes a NL after every line and that doesn't work in the terminal) 03:39:38 You can run it with qemu-system-x86_64 -kernel kernel-x86 04:04:43 --- quit: `presiden (Quit: WeeChat 2.6-dev) 04:07:36 --- join: iyzsong- joined #forth 04:07:38 --- quit: iyzsong (Ping timeout: 272 seconds) 04:08:42 --- quit: john_cephalopoda (Read error: Connection reset by peer) 04:08:54 --- join: john_cephalopoda joined #forth 04:15:08 --- join: xek__ joined #forth 04:30:06 --- join: dys joined #forth 05:10:59 --- quit: jsoft (Ping timeout: 265 seconds) 05:15:17 --- quit: actuallybatman (Ping timeout: 240 seconds) 05:44:44 What rdrop said the other day about new forthers biting off more than they can chew right away 05:44:49 I hope I'm not doing that 05:45:11 I am just trying to write a mostly 'conventional' forth, on a platform I enjoy writing for at a low level regularly 05:49:04 And then I want to try and solve some problems with it, and that I think is where it might actually become tailored somehow 05:52:44 --- quit: john_cephalopoda (Ping timeout: 265 seconds) 05:53:24 --- join: john_cephalopoda joined #forth 06:03:54 veltas: Z80? What platform? 06:15:56 --- quit: dave0 (Quit: dave's not here) 06:23:20 --- quit: Zarutian_HTC (Ping timeout: 260 seconds) 06:25:56 --- join: Zarutian_HTC joined #forth 07:04:45 --- quit: iyzsong- (Ping timeout: 260 seconds) 08:03:00 --- join: jsoft joined #forth 08:27:56 --- quit: ecraven (Ping timeout: 272 seconds) 08:36:55 --- join: ecraven joined #forth 08:40:21 --- quit: ecraven (Client Quit) 08:43:20 --- join: ecraven joined #forth 08:47:48 --- quit: ecraven (Ping timeout: 250 seconds) 09:20:52 --- join: dddddd joined #forth 09:35:49 --- quit: proteus-guy (Ping timeout: 256 seconds) 09:53:51 --- join: newuser|33 joined #forth 10:13:18 --- quit: newuser|33 (Remote host closed the connection) 10:19:48 --- quit: jsoft (Ping timeout: 264 seconds) 11:49:16 --- quit: john_cephalopoda (Remote host closed the connection) 11:49:33 --- join: john_cephalopoda joined #forth 11:59:22 --- join: kori joined #forth 11:59:22 --- quit: kori (Changing host) 11:59:22 --- join: kori joined #forth 12:18:37 --- quit: webchat9 (Ping timeout: 240 seconds) 12:54:10 --- quit: Zarutian_HTC (Remote host closed the connection) 12:54:26 --- quit: john_cephalopoda (Read error: Connection reset by peer) 12:54:35 --- join: john_cephalopoda joined #forth 13:49:15 --- join: Zarutian_HTC joined #forth 13:50:19 --- quit: gravicappa (Ping timeout: 256 seconds) 14:07:17 --- join: proteus-guy joined #forth 14:09:01 --- quit: proteus-guy (Max SendQ exceeded) 14:10:52 --- quit: proteusguy (Ping timeout: 265 seconds) 14:23:30 --- join: proteusguy joined #forth 14:23:30 --- mode: ChanServ set +v proteusguy 14:26:40 --- join: proteus-guy joined #forth 14:30:00 --- quit: dys (Ping timeout: 264 seconds) 14:31:39 --- quit: xek__ (Ping timeout: 265 seconds) 14:38:11 --- quit: john_cephalopoda (Quit: Leaving) 14:43:53 --- quit: Zarutian_HTC (Remote host closed the connection) 14:47:15 --- join: Zarutian_HTC joined #forth 15:09:53 --- join: dys joined #forth 16:22:30 --- join: actuallybatman joined #forth 16:26:30 --- quit: reepca (Read error: Connection reset by peer) 16:27:03 --- join: reepca joined #forth 16:54:13 --- join: jsoft joined #forth 17:54:42 --- quit: proteus-guy (Ping timeout: 256 seconds) 18:38:10 --- join: dave0 joined #forth 18:52:44 --- join: boru` joined #forth 18:52:47 --- quit: boru (Disconnected by services) 18:52:50 --- nick: boru` -> boru 19:18:00 --- quit: Zarutian_HTC (Ping timeout: 264 seconds) 19:32:02 --- join: Zarutian_HTC joined #forth 19:32:10 --- quit: jsoft (Ping timeout: 256 seconds) 19:34:46 --- join: iyzsong joined #forth 19:42:19 --- quit: dave0 (Quit: dave's not here) 19:43:37 --- join: proteus-guy joined #forth 19:45:18 --- join: karswell joined #forth 20:40:15 --- quit: karswell (Remote host closed the connection) 20:40:37 --- join: karswell_ joined #forth 20:41:09 --- quit: proteus-guy (Ping timeout: 256 seconds) 21:00:32 john_cephalopoda: is the source for your mandelbrot thingie available separately? 21:22:50 --- quit: actuallybatman (Ping timeout: 260 seconds) 21:29:28 --- quit: kori (Ping timeout: 272 seconds) 21:31:55 tpbsd: I see that your code use i within words 21:32:21 yes 21:32:27 are you relying on some ra magic to make that possible? 21:32:52 not that I'm aware off, i is just the loop counter 21:33:20 yeah, but normally the loop counter is kept on the return stack 21:34:05 i ( - -u|n ) Gives innermost loop index 21:34:05 j ( - -u|n ) Gives second loop index 21:34:06 k ( - -u|n ) Gives third loop index 21:34:14 Croran: http://forth.works/examples/mandelbrot.retro.html is an older copy of john's mandlebrot code 21:34:16 k and k are also available 21:35:01 tabemann_, I used I in my non RA days also 21:35:15 hmm 21:35:20 --- nick: tabemann_ -> tabemann 21:35:47 all code that runs on RA also runs on non RA afaik 21:36:03 --- quit: dddddd (Ping timeout: 256 seconds) 21:36:18 there are no "RA only" apps Ive seen 21:39:20 okay, just checked 21:39:37 i is always in a register, whereas j and k are on the return stack 21:40:13 ah! 21:40:26 but theyre still available in Mecrisp-Stellaris 21:40:37 --- join: webchat9 joined #forth 21:40:37 yes 21:41:31 RA Core Register Usage 21:41:31 Register Purpose Notes 21:41:31 r0 Free scratch register Saved on interrupt entry by hardware r1 Free scratch register Saved on interrupt entry by hardware r2: Free scratch register Saved on interrupt entry by hardware r3: Free scratch register Saved on interrupt entry by hardware 21:41:31 r4: Inner loop count Needs Push and Pop when used otherwise r5: Inner loop limit Needs Push and Pop when used otherwise 21:41:32 r6=TOS: Top-Of-Stack Stack design is interrupt safe ) r7=PSP: Parameter Stack Pointer Stack design is interrupt safe ) 21:41:35 r8: Unused r9: Unused r10: Unused r11: Unused r12: Unused Saved on interrupt entry by hardware 21:41:37 r13=SP: Return Stack Pointer r14=LR: Link Register r15=PC: Program Counter, always odd 21:42:57 yeah, zeptoforth's do loops are more expensive than that because they store all their info on the return stack in all cases 21:44:17 okay, am really sleepy, gonna hit the sack 21:44:20 g'night 21:44:25 cya 22:25:16 --- join: gravicappa joined #forth 22:52:51 --- join: crab1 joined #forth 22:53:01 What's up forth boys 22:54:39 --- join: jsoft joined #forth 22:56:28 welcome 23:14:02 --- quit: karswell_ (Ping timeout: 250 seconds) 23:59:59 --- log: ended forth/20.04.04