00:00:00 --- log: started forth/20.02.24 00:15:21 --- quit: dys (Ping timeout: 258 seconds) 00:53:32 --- quit: rdrop-exit (Quit: Lost terminal) 01:08:14 --- join: dys joined #forth 02:53:30 --- join: tp joined #forth 03:02:42 gahh C hardware examples are so frustrating! 03:03:30 mainly as the information needed to understand what the 'special' C syntax does is never in the example 03:04:30 consider this "TSC->CR = TSC_CR_PGPSC_2 | TSC_CR_PGPSC_0" 03:05:32 TSC_CR is a documented cortex-m register, no problem there 03:06:42 TSC_CR_PGPSC is also a documented register with three bits that can be set, i.e. TSC_CR_PGPSC ( %XXX -- ) 03:07:15 so Im guessing that TSC_CR_PGPSC_2 = %010 here ?? 03:07:39 and TSC_CR_PGPSC_0 = %001 here ?? 03:19:05 hmm what's required is TSC_CR_PGPSC = %101 03:19:32 so TSC_CR_PGPSC_2 means 'bit 2' 03:20:24 .. just as well they dont have 32 individual bits to define ;-) 03:41:48 luckily Forth lets me do it in one operation "%101 TSC_CR_PGPSC bis!" 04:51:04 --- quit: iyzsong (Quit: ZNC 1.7.1 - https://znc.in) 05:56:58 --- join: dddddd joined #forth 06:38:39 --- join: X-Scale` joined #forth 06:40:28 --- quit: X-Scale (Ping timeout: 240 seconds) 06:40:28 --- nick: X-Scale` -> X-Scale 06:54:39 --- quit: tp (Remote host closed the connection) 06:54:59 --- join: tp joined #forth 06:55:00 --- quit: tp (Changing host) 06:55:00 --- join: tp joined #forth 07:04:25 hey 07:08:56 Almost have a working basic (very) runtime compiler going for ActorForth! 07:09:02 TSC_CR_PGPSC_2 = %100 I think 07:09:17 hey proteus-guy 07:10:03 for me zeptoforth is awfully functional for something I only began debugging on wednesday and which is my first semi-working project in Thumb assembly 07:10:05 tabemann, howdy. 07:10:14 nice going! 07:10:39 right now it doesn't execute words properly when you enter them, but it complains when you enter something that it doesn't see as a word or a number 07:10:53 I have to figure out why it's not executing words yet 07:12:17 it took a while to get the last-word-in-flash lookup working properly 07:19:14 YES 07:19:32 I got immediate word execution working 07:19:58 it was a very stupid bug - I switched around the test for interpretation mode and compilation mode by accident 07:21:23 --- join: jsoft joined #forth 07:23:47 okay, gotta get ready for work 07:28:08 --- quit: tabemann (Ping timeout: 240 seconds) 08:11:26 --- quit: X-Scale (Ping timeout: 255 seconds) 08:12:48 --- join: X-Scale` joined #forth 08:14:34 --- nick: X-Scale` -> X-Scale 08:14:56 --- join: xek_ joined #forth 08:17:33 --- quit: xek (Ping timeout: 272 seconds) 09:37:28 --- quit: dys (Ping timeout: 240 seconds) 10:56:13 --- join: dys joined #forth 11:37:45 --- join: WickedShell joined #forth 11:45:54 Hyphens or underscores? 11:58:23 hyphens 11:58:44 Actually I have a real question 11:59:16 Do Forths typically use the actual 'stack' for the return stack, or do they tend to put return stack somewhere else? 12:04:34 two separate stacks, one for data, one for return addresses 12:04:39 Yes I get that 12:04:50 I mean like the stack maintained by a special register, usually called 'SP' 12:04:56 --- quit: tp (Read error: Connection reset by peer) 12:05:07 in terms of hardware, it'd depend on the implementation 12:05:10 That is the 'return stack' on many architectures, including Z80 which is what I'm writing for right now 12:05:24 I'm just wondering if it's a bad idea to use that stack as my 'return stack' 12:05:28 in my old x86 system, I used the hardware stack for return addresses 12:05:52 Like if I'm going to shoot myself in the foot by doing that 12:07:34 are you dealing with a host os, or running on the hardware directly? 12:08:46 Hardware directly 12:09:18 --- join: tp joined #forth 12:09:18 --- quit: tp (Changing host) 12:09:18 --- join: tp joined #forth 12:09:50 i'd think you'd be fine then, as you'll have full control of everything 12:10:41 Hmm, okay thanks 12:11:13 It can only go so wrong, after all forth implementations aren't meant to be that big 12:33:55 on a unix host, mine has 497 words, of which 60 are in the kernel, 262 are in the standard library, and 175 are platform-specific 12:52:18 veltas, I've been disconnected so didnt see CRC's reply. The Forth I use, Mecrisp-Stellaris has two separate stacks, the data stack and the return stack 12:57:35 veltas: my z80 Forth uses a simulated stack for the return stack 12:57:41 the data stack is just the processor's normal stack 12:59:20 --- quit: gravicappa (Ping timeout: 258 seconds) 13:40:29 --- quit: reepca (Ping timeout: 260 seconds) 13:50:55 --- join: dave0 joined #forth 13:55:57 --- join: reepca joined #forth 14:34:59 siraben: That makes sense as well because of the PUSH/POP efficiency 14:35:00 veltas, if your hardware has another register with addressing options that support a second stack (6809 was good for this) then you take advantage of it, but most CPUs you have to fake it. 14:35:06 Even without CALL/RET 14:35:28 proteus-guy: On Z80 the byte at (HL) can be treated like a slow 8-bit register 14:36:03 So for most purposes (HL) is your good 'second' choice for memory access, but the stack is just far superior in access speed, especially dealing with 16-bit words 16:41:38 --- join: iyzsong joined #forth 17:11:37 --- join: tabemann joined #forth 17:18:36 tp! 17:18:53 I got zeptoforth to successfully execute 3 3 + . 17:57:37 --- quit: tabemann (Ping timeout: 260 seconds) 18:25:56 --- quit: WickedShell (Remote host closed the connection) 18:27:19 --- join: boru` joined #forth 18:27:22 --- quit: boru (Disconnected by services) 18:27:25 --- nick: boru` -> boru 19:14:33 --- join: tabemann joined #forth 19:15:08 --- quit: tabemann (Remote host closed the connection) 19:15:15 --- join: tabemann joined #forth 19:15:50 --- quit: tabemann (Remote host closed the connection) 19:15:57 --- join: tabemann joined #forth 19:51:30 --- quit: djinni (Ping timeout: 260 seconds) 19:52:26 --- quit: KipIngram (Ping timeout: 260 seconds) 19:52:35 --- join: djinni joined #forth 19:52:49 --- join: KipIngram joined #forth 19:52:59 --- quit: reepca (Ping timeout: 260 seconds) 19:53:12 --- nick: KipIngram -> Guest30789 19:54:24 --- join: reepca joined #forth 20:08:29 tp you animal, how goes it 20:33:25 --- quit: _whitelogger (Remote host closed the connection) 20:36:28 --- join: _whitelogger joined #forth 20:38:13 tp is usually livelier at this time of the day 20:43:04 okay, I'm gonna hit the sack 20:44:35 --- quit: dave0 (Quit: dave's not here) 21:10:01 --- quit: dys (Ping timeout: 240 seconds) 21:15:03 --- nick: Guest30789 -> KipIngram 21:15:26 --- mode: ChanServ set +v KipIngram 21:31:49 --- join: gravicappa joined #forth 21:35:45 tabemann, awesome!!! 21:48:04 --- quit: nonlinear5 (Quit: The Lounge - https://thelounge.chat) 21:48:18 --- join: nonlinear joined #forth 22:49:13 --- quit: dddddd (Ping timeout: 240 seconds) 23:05:20 --- quit: iyzsong (Quit: ZNC 1.7.1 - https://znc.in) 23:05:40 --- join: iyzsong joined #forth 23:11:54 tabemann, nice! And don't you mean "hit the stack"? ;-) 23:22:22 --- quit: proteus-guy (Quit: Leaving) 23:59:59 --- log: ended forth/20.02.24