Daniel Thornburgh

> > Yes, because it's trying to fit `$1602` into eight bits :-) > > Ok, I rejected the idea as wrong anyway. I just thought that I might be...

> > so that it doesn't check that bits 8-15 of the 32-bit virtual address for the symbol are zero. > > That's insufficient - there's still the `LTO` zero...

> Yes, But if the BP register is set to $16, you would automatically accessing $1602 if you use the address $02.. Thus, starting the Zero-Page with $02 is still...

> > But, for zero page pointers, there isn't actually enough information available at runtime to extend the pointer. > > Actually, now that I think about it again, there...

So here's my thoughts. (Apologies if this retreads some ground already discussed; I'd only been loosely following the discussion.) Imaginary registers pull a lot of weight. Like modern registers, they...

> It's a decent proposal, thouh I would make sure to limit the changes to the compiler only. If we do it by adding a new address space (`__basepage`) which...

> I was considering the idea of introducing a relocation type for this particular use case... Namely, there might be a new relocation that emits a tab instruction inline if...

> 1. Do you want this to support C= C65 prototypes with their 4510, or only the MEGA65 and its 45GS02? This has important consequences, because ... I think if...

It looks like this comes with the additional requirement to specify format strings for these types in `inttypes.h`. That will be difficult without getting really creative with the printf format...

No, this is about the code generated for the actual `__memset` libcall implementation in the SDK.