00:00:00 --- log: started forth/19.06.06 02:02:29 --- quit: ashirase (Ping timeout: 245 seconds) 02:06:57 --- join: ashirase (~ashirase@modemcable098.166-22-96.mc.videotron.ca) joined #forth 02:45:49 Assembler written as a DSL in RETRO: http://thecutecuttlefish.org/tmp/asmm.png 03:05:09 --- join: [1]MrMobius (~default@c-73-134-82-217.hsd1.va.comcast.net) joined #forth 03:09:13 --- quit: MrMobius (Ping timeout: 272 seconds) 03:09:14 --- nick: [1]MrMobius -> MrMobius 03:11:16 nice! 03:48:10 --- join: dddddd (~dddddd@unaffiliated/dddddd) joined #forth 04:10:52 john_cephalopoda: if you want to have hex numbers for the assembler, you could try this: http://forth.works/6f51b558c26572753ccb43c4fb1608da 05:02:44 --- join: X-Scale (~ARM@167.247.28.37.rev.vodafone.pt) joined #forth 07:08:04 --- quit: rdrop-exit (Quit: Lost terminal) 07:41:52 --- quit: tabemann (Ping timeout: 248 seconds) 07:42:56 --- join: xek_ (xek@nat/redhat/x-ezzddqtbjbnvqpmu) joined #forth 07:43:31 --- quit: xek (Read error: Connection reset by peer) 08:08:28 john_cephalopoda, that's yours? how long did it take you to develop? I've not made an x86 assembler before. Seems a lot more effort than 6809s and RISC cpus. :-) 08:13:15 proteusguy: Right now it only supports a handful of commands. Extending is simple though. 08:13:31 Here is a gforth version that is a bit further than the retro version: https://github.com/jmf/impexus/blob/master/arch/x86/asm_x86.fth 08:14:30 I concentrate on implementing a relatively small set of commands, which I can then use like RISC. 08:17:14 nice. this is for writing something like a self-contained boot loader? 08:17:52 Not only a bootloader, a whole OS :D 08:18:09 I can run it on top of syslinux. 08:18:16 (Which is a bootloader) 08:19:18 I planned to write the core in this Assembly-like DSL and build onto it with Forth to have something self-hosting very quickly. 08:19:48 But maybe I'll port it to Retro and then put a Retro implmentation on top of it. 08:19:51 Yeah that's what I meant... what's the memory model x86 starts up in again? I forget. I know it's not flat. One of the segmented models as I recall. 08:24:12 --- quit: john_cephalopoda (Ping timeout: 258 seconds) 08:25:37 --- join: john_cephalopoda (~john@unaffiliated/john-cephalopoda/x-6407167) joined #forth 08:25:47 Oops, sorry, I lost connection there. 08:26:07 x86 goes into Real Mode at startup, which has no memory segmentation, as far as I know. 08:26:33 It only has limited memory though. Once in Protected Mode, you got more memory but have to mess with an MMU 08:26:45 That 8086 mode correct? 16 bit. 08:42:20 Real Mode is the one that ORIGINATED segmentation in popular CPUs, john_cephalopoda. 08:42:37 20-bit address space, but 16-bit address registers. 08:43:04 So you had a segment register shifted left four spaces and added to an offset register to get your physical address. 09:07:35 --- quit: lchvdlch (Changing host) 09:07:35 --- join: lchvdlch (~nestr0@pdpc/supporter/active/lchvdlch) joined #forth 09:19:59 09:20:01 09:20:01 09:20:05 whoops sorry 09:20:28 i was further up and my ocd obliged me to hit the same keys with each hand 09:45:36 --- quit: xek_ (Ping timeout: 248 seconds) 10:16:53 you have three hands? 10:17:03 --- join: dys (~dys@tmo-102-78.customers.d1-online.com) joined #forth 10:51:25 --- join: Keshl_ (~Purple@207.44.70.214.res-cmts.gld.ptd.net) joined #forth 10:52:20 --- quit: Keshl (Read error: Connection reset by peer) 11:00:52 Three hands would come in awfully handy sometimes. 11:01:25 i get it 12:37:19 --- quit: gravicappa (Ping timeout: 272 seconds) 14:01:34 --- join: dave0 (~dave0@069.d.003.ncl.iprimus.net.au) joined #forth 14:02:01 hi 14:05:30 hi 14:07:42 hi rain1 14:07:52 * crc continues playing with sockets: http://forth.works/de8d935c86f8f3ee128944ff031b90ba.html 14:21:26 looks a bit forth-y 14:28:09 --- quit: reepca (Ping timeout: 272 seconds) 15:07:16 crc: you got the usual system-calls for sockets and such as Forth-y runtime-primitives? 15:29:40 --- quit: dave0 (Quit: dave's not here) 15:32:27 --- join: dave0 (~dave0@069.d.003.ncl.iprimus.net.au) joined #forth 16:28:22 --- quit: Zarutian (Read error: Connection reset by peer) 16:29:20 --- join: Zarutian (~zarutian@173-133-17-89.fiber.hringdu.is) joined #forth 16:45:50 --- join: TheCephalopod (~john@unaffiliated/john-cephalopoda/x-6407167) joined #forth 16:49:03 --- quit: john_cephalopoda (Ping timeout: 268 seconds) 17:08:48 --- part: moony left #forth 17:11:40 --- join: tabemann (~travisb@h193.235.138.40.static.ip.windstream.net) joined #forth 17:20:51 Zarutian: pretty much 17:21:04 words are listed at http://forth.works/ff9533e3f47cdf284bae9eb842dbf8d3 17:23:06 dave0: it is forth... 17:24:38 crc: hmm... how does one do the equiv of the select or poll system call? or otherwise do non-blocking stuff? 17:24:55 that's not started yet 17:25:15 I see 17:26:48 crc: and why are stack diagrams in retro so unconventional from Forth? 17:28:16 --- join: epony (~epony@unaffiliated/epony) joined #forth 17:30:08 (1) retro has used shorthand notation for the stack comments for many years (2) less typing (3) personal preference [I prefer (an-) over something like (_address_length_--_) ] 17:30:57 I see 17:33:59 --- quit: epony (Remote host closed the connection) 17:47:05 I didn't use stack comments until retro10, which was where I started using this short notation 17:48:23 this was in 2008, so I've used these for a decade now 17:59:43 --- quit: tabemann (Ping timeout: 246 seconds) 18:18:43 /c/c 19:35:57 --- nick: Keshl_ -> Keshl 19:38:26 --- join: tabemann (~travisb@2600:1700:7990:24e0:b944:a349:56b9:12fb) joined #forth 19:38:32 --- part: tabemann left #forth 19:39:30 --- join: tabemann (~travisb@2600:1700:7990:24e0:b944:a349:56b9:12fb) joined #forth 19:47:44 --- join: rdrop-exit (~markwilli@112.201.166.63) joined #forth 19:56:27 --- quit: cantstanya (Remote host closed the connection) 19:58:52 --- join: cantstanya (~chatting@gateway/tor-sasl/cantstanya) joined #forth 20:43:26 --- join: gravicappa (~gravicapp@h83-174-253-143.dyn.bashtel.ru) joined #forth 21:19:00 --- join: reepca (~user@208.89.170.37) joined #forth 21:23:10 --- quit: dave0 (Quit: dave's not here) 21:29:19 --- quit: rdrop-exit (Ping timeout: 272 seconds) 21:34:57 --- quit: dddddd (Remote host closed the connection) 22:11:23 Anyone done much unit testing for their forth code? I always did but I rarely ever see people do theirs. Perhaps because they code bottom up at the repl and just never save their test cases? 23:42:32 --- quit: jedb (Remote host closed the connection) 23:43:11 --- join: jedb (~jedb@185.128.24.51) joined #forth 23:44:00 --- quit: jedb (Remote host closed the connection) 23:44:20 --- join: jedb (~jedb@185.128.24.51) joined #forth 23:59:30 --- join: dave0 (~dave0@069.d.003.ncl.iprimus.net.au) joined #forth 23:59:59 --- log: ended forth/19.06.06