Denial

the register map of FE3 surely is less complicated than the one of Ultimem. I just skimmed over the docs for both and find the Ultimem one much easier to grasp. FE3 is certainly more complicated. Ultimem seems straightforward and everything makes sense on first look. It also seems to be much more f...

My last effort to get anything done in wikipedia was the german "Rasterzeileninterrupt" article (have a look at the discussion pages for LOTS of WTF)

Very likely, that once had been a conclusion by analogy as the first VIC-II revision in the C64 actually only had 5 luminance levels and someone thought it must have been the same with VIC-I.

That would be my guess as well.

Hooray for original research \o/

Damn Lisp.... There also was a Lisp implementation Input64 mag, if you want to look at it

Unless you cheat and use pretend 3D

Even then really, far from trivial.

This isn't trivial to do even in assembly

I'm not complaining at all. It's just a pretty silly thing to say. Especially about cc65 - it's neither "bloated" nor is it excessively commented. Quite the contrary is true - It's actually lacking a lot in that area.

IMHO comments should be used exclusively if the life of a developer depends on them but at least never tell what the code is already screaming about.

Hopefully you never write any software that someone else has to work with

the Small-C type compilers often seem to convert byte-arithmetic to 16 bits (via virtual ZP registers) for work, converting back to BYTE at the end - which is very inefficient. One reason for that are the integer promotion rules of C though. I'd expect most c-compilers doing this actually - just th...

You could just port the atari version (which later became cc65)

Yeah good luck What makes cc65 strong is the library and its ecosystem anyway, and if you rely on the optimizer of a 8bit compiler, you are doing it wrong

cc65 cant really do more than it does now (peephole optimizations) - it has to be rewritten to use an IR first - acqn has been working on it iirc, check his repos

In general, with user-written code, an assembler will not have a good idea about these conditions. It amounts to execute arbitrary code already in the assembler which, IMO, is not its job. Peephole optimization is well possible in an assembler. Actually Daniel Dallmann (Lunix) wrote such optimizer ...

Couldn't you make it generate the reset signal as well (would require a patch cable of ofcourse)?

I would love if someone made a small assembler like ASM502 for the ARM, targeting the pi, android, Arduino, blue pill etc, so you didn't have to run an SDK full of bugs taking a gigabyte or more.. Just build GAS for ARM? For all those modern CPUs it really doesn't make a lot of sense to make a cust...