Checked CINT on TRS80 and it does truncate (same like FIX) instead of round to nearest for some reason. And also noticed that INT on VC83 truncates instead of flooring.

Name it "CINT". That's how it is called elsewhere and saves a byte too.

I did one for the 12F675 (4 MHz) at 1200 baud. Does twice the interrupt rate in the duplex case with alternating intervals on the same timer. Unless rx/tx is close as then both are done in the same interrupt with a constant rate. Works nicely in simulator also at higher baud rates and faster ...

Quick hack I did yesterday for testing. The original was for CBM PET and was adapted to use VT100 control sequences. Might be too fast on some systems with high baud rates. But is usable on my setup (~1.7Mhz and 38400N1).
0 REM BASED ON ORIGINAL PETRIS (C)2002 CURTIS F KAYLOR
10 E$=CHR$(27)+"[":R ...

I wanted to use them for a current project but it's annoying that with a 65C02 these are zero page bound. However the bit instructions are much more usable with a 65CE02 where the base page is movable:

.0889 irq .proc
.with io.u1
.0889 48 pha
.088a a9 20 lda #pir.RCIF
.088c 2c 0f 27 bit pir
.088f ...

soci, is that .asm code for the 64Tass assembler? It'd be good if you could add some comments of explanation for those of us not familiar with that assembler. I am unfamiliar with most of those assembler directives (at least I guess that's what they are, starting with a dot).
Yes, those are 64tass ...

Hello laztrezort!

I'd recommend an alternate approach by stacking namespaces instead of branch instruction locations.

The advantage is that it's possible to define symbols like _skip or _loop in them. Using these as branch destinations there's no need for patching with .byte directives. Error ...

The equivalent is easy to do:

strTop .function _s : bytes
.text _s[:-1], _s[-1] | $80
.endf

.strTop "test"
It converts the parameter to bytes first and then cuts of the last one and sets the sign bit there. Same could be done directly on the string as well but that would break escape ...

Thank you for replying to the issues I encountered. I will go back and try the option to get a simple binary file. Nice to know that the author is contactable.

There's also an e-mail address as the bug tracker needs registration. Prompt answers are not guaranteed, needs a bit of a luck sometimes ...

Not too surprisingly I use this one:

https://tass64.sourceforge.net/

If the latest version isn't packaged yet it's easy to compile it.
I downloaded the above from a repo on Github.

Thanks for checking it out! If it was from Irmen's unofficial mirror then you were lucky this time as currently ...

Not too surprisingly I use this one:

https://tass64.sourceforge.net/

If the latest version isn't packaged yet it's easy to compile it.

Neither PB or PC can modified by a copy from another register or by a stack pull instruction. For instance, it's not possible to simply load a general-purpose register with a value and copy it to either of those registers, even through the stack. Another for instance: while it's possible to change ...

Another typo (7A vs. 71):
T9e9 HEX 00,1A,71,18,02

Don't forget to apply the other 2 corrections above.

Please post an example source code for such a simple hello world program and its Makefile. If it's short a hex dump of the expected result would be nice as well.

Thanks!

The .assert and .check directives in 64tass are not for code testing purposes as outlined above.

These directives were added long time ago to prevent mistakes when programming banked memory systems. I needed them because often the wrong memory configuration was used which resulted in memory ...