Activity for ACME Cross-Assembler

Jake Hamby posted a comment on discussion General Discussion

Jake Hamby — Tue, 21 Apr 2026 15:38:00 -0000

The following line doesn't work for me (including with the latest ACME source code): and #!$C0 Error - File basic3.asm, line 1793 (Zone ): Number does not fit in 8 bits. I worked around it by changing the line to "and #$5F" but it's strange. I tried using "and+1" but that didn't help. Everything else looks great! -Jake

Marco Baye committed [r449] on Code

Marco Baye — Sun, 16 Nov 2025 18:42:51 -0000

fixed confusing "no string given" error message, now there are separate

Piero Furiesi modified a comment on ticket #30

Piero Furiesi — Fri, 10 Oct 2025 10:52:58 -0000

Solved. Maybe there's something wrong in ACME when calculating (+) reference. !macro BEQ .l { !set .b = (* - 126 <= .l) & (.l <= * + 129) !ifdef .b {!if .b { BEQ .l } else { BNE * + 5: JMP .l}} }

Piero Furiesi posted a comment on ticket #30

Piero Furiesi — Fri, 10 Oct 2025 10:52:20 -0000

Solved. Maybe there's something wrong in ACME when calculating (+) reference. !macro BEQ ~.l { !set .b = (* - 126 <= .l) & (.l <= * + 129) !ifdef .b {!if .b { BEQ .l } else { BNE * + 5: JMP .l}} }

Piero Furiesi posted a comment on ticket #30

Piero Furiesi — Fri, 10 Oct 2025 10:32:35 -0000

... But this one fails (why?) * = $C000 +LBL ~mylabel !for .i, 1, 10 {NOP} +BEQ mylabel ;short !for .i, 1, 200 {NOP} +BEQ mylabel ;long !for .i, 1, 200 {NOP} +BEQ mylabel ;long !for .i, 1, 200 {NOP} +BEQ mylabel ;long -- FAILURE

Piero Furiesi modified a comment on ticket #30

Piero Furiesi — Fri, 10 Oct 2025 10:14:16 -0000

;THIS WORKS! ;ACME release 0.97 ("Zem"), 1 Aug 2025 ;define .l as a target for a (long) branch. "LBL is a Long Branch LBL." !macro LBL ~.l { !set .l = * } ;long branches: .l must be a label defined by +LBL macro !macro BEQ .l { !set .b = (* - 126 <= .l) & (.l <= * + 129) !ifdef .b {!if .b { BEQ .l } else { BNE + : JMP .l :+ }} } * = $C000 +BEQ mylabel ;long !for .i, 1, 200 {NOP} +BEQ mylabel ;short !for .i, 1, 10 {NOP} +LBL ~mylabel !for .i, 1, 10 {NOP} +BEQ mylabel ;short !for .i, 1, 200 {NOP} +BEQ...

Piero Furiesi modified a comment on ticket #30

Piero Furiesi — Fri, 10 Oct 2025 10:13:36 -0000

Piero Furiesi posted a comment on ticket #30

Piero Furiesi — Fri, 10 Oct 2025 10:11:59 -0000

;THIS WORKS! ;ACME release 0.97 ("Zem"), 1 Aug 2025 ;define .l as a target for a (long) branch. "LBL is a Long Branch LBL." !macro LBL ~.l { !set .l = * } ;long branches: .l must be a label defined by +LBL macro !macro BEQ .l { !set .b = (* - 126 <= .l) & (.l <= * + 129) !ifdef .b {!if .b { BEQ .l } else { BNE + : JMP .l :+ }} } = $C000 +BEQ mylabel ;long !for .i, 1, 200 {NOP} +BEQ mylabel ;short !for .i, 1, 10 {NOP} +LBL ~mylabel !for .i, 1, 10 {NOP} +BEQ mylabel ;short !for .i, 1, 200 {NOP} +BEQ...

Marco Baye committed [r448] on Code

Marco Baye — Sat, 09 Aug 2025 15:37:56 -0000

added a comment on where to fix a bug

Marco Baye modified ticket #30

Marco Baye — Tue, 29 Jul 2025 20:50:06 -0000

Re-assembling alternate code after error

Marco Baye posted a comment on ticket #30

Marco Baye — Tue, 29 Jul 2025 20:49:43 -0000

Once version 0.98 is released, it should be possible to do stuff like this using macro magic. ...and for CPUs that have "long" branches (like 65ce02), choosing the correct length could be done automatically. Version 0.98 will be out RealSoonNow (tm).

Marco Baye committed [r447] on Code

Marco Baye — Tue, 29 Jul 2025 20:33:11 -0000

added "!break", "!continue" and "!return" (for loops and macros, respectively)

Piero Furiesi modified a comment on ticket #30

Piero Furiesi — Wed, 23 Jul 2025 08:01:47 -0000

Ticket to close. I've thought about it again. This feature might only be useful for the "Target out of range" error, and a shell script that modifies the source file and re-invokes acme is much better.

Piero Furiesi modified a comment on ticket #30

Piero Furiesi — Wed, 23 Jul 2025 08:01:01 -0000

Ticket to close. I've thought about it again. This feature might only be useful for the "Target out of range" error, and a shell script that modifies the source file and reactivates acme is much better.

Piero Furiesi posted a comment on ticket #30

Piero Furiesi — Mon, 21 Jul 2025 10:51:00 -0000

I missed some colon, last code shoud read as {BCS + : JMP some_addr : +}

Piero Furiesi created ticket #30

Piero Furiesi — Mon, 21 Jul 2025 10:45:47 -0000

Re-assembling alternate code after error

Piero Furiesi posted a comment on ticket #12

Piero Furiesi — Sat, 19 Jul 2025 15:40:32 -0000

Hi, I saw that !info & !debug pseudoopcodes have been added since [r332], many thanks! Documentation in docs/AllPOs.txt should be updated too ;)

Marco Baye committed [r446] on Code

Marco Baye — Fri, 11 Jul 2025 09:17:28 -0000

moved test files around

Marco Baye committed [r445] on Code

Marco Baye — Thu, 10 Jul 2025 22:55:09 -0000

fixed bug where "!if" complained about undefined conditions even if user had

Marco Baye committed [r444] on Code

Marco Baye — Thu, 10 Jul 2025 21:49:28 -0000

"else if" can now also be written as "elif"

Marco Baye committed [r443] on Code

Marco Baye — Thu, 10 Jul 2025 10:55:16 -0000

added FIXMEs

Marco Baye committed [r442] on Code

Marco Baye — Mon, 23 Jun 2025 10:46:15 -0000

"fix" for previous commit

Marco Baye committed [r441] on Code

Marco Baye — Sun, 22 Jun 2025 21:31:25 -0000

added "denial of service" example source code

Marco Baye committed [r440] on Code

Marco Baye — Thu, 19 Jun 2025 15:55:24 -0000

small cleanup in src and docs concerning ACME library

Marco Baye committed [r439] on Code

Marco Baye — Tue, 17 Jun 2025 11:17:39 -0000

added some comments and "!byt" and "!outfilestop" aliases.

Marco Baye committed [r438] on Code

Marco Baye — Mon, 16 Jun 2025 21:15:38 -0000

added CLI option to override path to ACME library

Marco Baye committed [r437] on Code

Marco Baye — Thu, 08 May 2025 21:25:27 -0000

minor change in arrangement of mnemo tables

Marco Baye modified ticket #29

Marco Baye — Wed, 07 May 2025 13:00:07 -0000

Left shift by 24 errors on small numbers

Marco Baye modified ticket #23

Marco Baye — Wed, 07 May 2025 12:59:20 -0000

MEGA65: Most Q-instructions "don't" support indexed addressing mode

Marco Baye modified ticket #23

Marco Baye — Wed, 07 May 2025 12:58:44 -0000

MGEA65: Most Q-instructions "don't" support indexed addressing mode

Marco Baye posted a comment on ticket #23

Marco Baye — Wed, 07 May 2025 12:58:28 -0000

Fixed LDQ, the others had already been fixed earlier. If you don't build ACME from source, you'll have to wait a few more days, but version 0.98 will be released RealSoonNow(tm).

Marco Baye modified ticket #22

Marco Baye — Wed, 07 May 2025 12:56:42 -0000

MEGA65: LDQ (zp),Z and LDQ [zp],Z are supported

Marco Baye posted a comment on ticket #22

Marco Baye — Wed, 07 May 2025 12:56:12 -0000

Fixed. If you don't build ACME from source, you'll have to wait a few more days, but version 0.98 will be released RealSoonNow(tm).

Marco Baye committed [r436] on Code

Marco Baye — Wed, 07 May 2025 11:08:21 -0000

fixed addressing modes for M65 cpu (see tickets 22 and 23)

Marco Baye committed [r435] on Code

Marco Baye — Sun, 04 May 2025 17:47:12 -0000

updated link in docs to "No More Secrets" document

Dan Sanderson posted a comment on ticket #29

Dan Sanderson — Tue, 04 Mar 2025 01:27:06 -0000

Oh good! I was hoping it was something like that. My intuition was to add the zeroes so that there would be zeroes for >>24 to shift, i.e. so it didn't try to shift a 16-bit value 24 spaces and complain another way. If there's an existing path forward, I'll use it. ty!

Marco Baye posted a comment on ticket #29

Marco Baye — Tue, 04 Mar 2025 01:17:54 -0000

The problem is not the left shift, but the leading zeroes: Using "$001600" instead of "$1600" marks the value internally with a flag for "the user wants an oversized addressing mode", which then causes the error because "lda #0" cannot be encoded with a 24-bit argument. You can a) remove the superfluous leading zeroes or b) use the command line switch "--ignore-zeroes" to disable this mechanism completely. I'll try to improve the docs for this error message.

Dan Sanderson created ticket #29

Dan Sanderson — Sat, 01 Mar 2025 07:23:50 -0000

Left shift by 24 errors on small numbers

Marco Baye committed [r434] on Code

Marco Baye — Sun, 26 Jan 2025 16:51:27 -0000

updated toacme: v0.19 now has support for the "C128 Top-Assembler".

Marco Baye modified ticket #21

Marco Baye — Mon, 25 Nov 2024 12:08:49 -0000

Macros as parameters to other macros

Marco Baye modified ticket #26

Marco Baye — Mon, 25 Nov 2024 12:07:59 -0000

MEGA65 PLW mnemonic missing?

Marco Baye modified ticket #27

Marco Baye — Mon, 25 Nov 2024 12:07:33 -0000

Pass strings in command line arguments

Marco Baye modified ticket #28

Marco Baye — Mon, 25 Nov 2024 12:06:57 -0000

Support for \x hex values in strings

Marco Baye posted a comment on ticket #27

Marco Baye — Mon, 25 Nov 2024 12:04:57 -0000

I implemented it, please re-test. Note that in order to be able to tell 42 and "42" apart, string values must be given in double quotes. But shells like bash remove these, so in bash the given example would have to look like this: acme -D FOO=\"BAR\" file.a

Marco Baye committed [r433] on Code

Marco Baye — Mon, 25 Nov 2024 00:44:38 -0000

the "-D" switch can now assign strings in double quotes (but check your shell's quoting rules!)

Marco Baye committed [r432] on Code

Marco Baye — Sat, 23 Nov 2024 14:51:03 -0000

reworked previous commit, added error checking and test cases

Marco Baye committed [r431] on Code

Marco Baye — Sat, 23 Nov 2024 14:41:39 -0000

added support for \x hex values in strings (thanks to Gurce for the patch, see ticket #28)

Marco Baye posted a comment on ticket #28

Marco Baye — Sat, 23 Nov 2024 12:56:10 -0000

Thanks for the patch, I'll merge it. It will be included in the 0.98 release.

Marco Baye posted a comment on ticket #27

Marco Baye — Sat, 23 Nov 2024 12:51:42 -0000

Yes, at the moment the "-D" switch only accepts numbers. Accepting strings is on the TODO list. Implementing this wouldn't be that difficult, but then I'd have to explain shell quoting rules in the docs. ;)

Gurce created ticket #28

Gurce — Tue, 19 Nov 2024 01:19:07 -0000

Support for \x hex values in strings

Timo Taipalus created ticket #27

Timo Taipalus — Sun, 10 Nov 2024 11:12:49 -0000

Pass strings in command line arguments

Marco Baye committed [r430] on Code

Marco Baye — Sun, 27 Oct 2024 12:56:54 -0000

updated list of warnings/errors

Marco Baye committed [r429] on Code

Marco Baye — Sun, 27 Oct 2024 12:42:39 -0000

file names can now be specified via string symbols

Marco Baye committed [r428] on Code

Marco Baye — Wed, 23 Oct 2024 12:32:27 -0000

refactored handling of dialects, newest behavior is now always given first

Gurce modified a comment on ticket #26

Gurce — Mon, 21 Oct 2024 02:56:31 -0000

Oops, pardon me, checking the mega65 manual, there is now PLW, ok, nevermind then, welcome to cancel the ticket :D

Gurce posted a comment on ticket #26

Gurce — Mon, 21 Oct 2024 02:56:02 -0000

Oops, pardon me, checking the mega65 manual, there is now PLW, ok, nevermind then, will cancel the ticket :D

Gurce created ticket #26

Gurce — Mon, 21 Oct 2024 02:46:32 -0000

MEGA65 PLW mnemonic missing?

Marco Baye committed [r427] on Code

Marco Baye — Sun, 20 Oct 2024 22:19:39 -0000

renamed a function and changed some comments, no change in functionality

Olaf Seibert posted a comment on ticket #25

Olaf Seibert — Mon, 07 Oct 2024 16:21:53 -0000

Great, that seems to work and produce the same program files as before. I plan to package this version for pkgsrc.

Marco Baye committed [r426] on Code

Marco Baye — Mon, 07 Oct 2024 11:13:49 -0000

cleaned up previous fix

Marco Baye modified ticket #25

Marco Baye — Mon, 07 Oct 2024 08:46:19 -0000

Incompatible change

Marco Baye posted a comment on ticket #25

Marco Baye — Mon, 07 Oct 2024 08:45:43 -0000

Thanks for reporting this. It looks like I created this bug in r419. It should be fixed in r424, please re-test.

Marco Baye committed [r425] on Code

Marco Baye — Mon, 07 Oct 2024 08:34:56 -0000

added regression test for previous fix

Marco Baye committed [r424] on Code

Marco Baye — Sun, 06 Oct 2024 23:21:01 -0000

fixed bug introduced in rev 419 (see ticket #25, thanks for reporting!)

Olaf Seibert created ticket #25

Olaf Seibert — Thu, 03 Oct 2024 14:47:08 -0000

Incompatible change

Marco Baye committed [r423] on Code

Marco Baye — Sun, 08 Sep 2024 09:55:01 -0000

refactored string handling

Marco Baye committed [r422] on Code

Marco Baye — Thu, 05 Sep 2024 22:18:30 -0000

refactored !bin, !fill and !align a bit

Marco Baye committed [r421] on Code

Marco Baye — Thu, 05 Sep 2024 11:48:07 -0000

refactored last commit

Marco Baye committed [r420] on Code

Marco Baye — Thu, 05 Sep 2024 09:47:50 -0000

now ignores BOM at start of source file

Marco Baye committed [r419] on Code

Marco Baye — Tue, 03 Sep 2024 10:01:44 -0000

fixed bug where "!skip" areas at start/end were included in output file

Marco Baye committed [r418] on Code

Marco Baye — Tue, 03 Sep 2024 09:49:13 -0000

fixed bug where a segment warning could cause another segment warning to disappear

Marco Baye committed [r417] on Code

Marco Baye — Tue, 03 Sep 2024 00:11:43 -0000

refactored "segment list" functions

Marco Baye committed [r416] on Code

Marco Baye — Mon, 02 Sep 2024 22:36:32 -0000

moved segment checks to final pass, made v0.98 force --strict-segments

Marco Baye committed [r415] on Code

Marco Baye — Sun, 01 Sep 2024 17:59:07 -0000

throwing of some errors can now be delayed until symbol changes are done

Marco Baye committed [r414] on Code

Marco Baye — Sun, 01 Sep 2024 16:23:10 -0000

small fix so "label" and "label=*" throw the same error if pc undefined

Marco Baye committed [r413] on Code

Marco Baye — Sun, 01 Sep 2024 13:50:37 -0000

a bit of refactoring concerning "unpseudopc"

Marco Baye committed [r412] on Code

Marco Baye — Sat, 31 Aug 2024 20:28:51 -0000

fixed bug in anonymous backward labels

Marco Baye committed [r411] on Code

Marco Baye — Sat, 31 Aug 2024 14:55:42 -0000

tiny refactoring

Marco Baye committed [r410] on Code

Marco Baye — Fri, 30 Aug 2024 19:49:37 -0000

added code so release 0.98 will always use the smallest possible addressing mode

Marco Baye committed [r409] on Code

Marco Baye — Fri, 30 Aug 2024 16:54:58 -0000

added dec() and hex() functions

Marco Baye posted a comment on ticket #21

Marco Baye — Fri, 30 Aug 2024 10:25:40 -0000

Yes, that is to be expected: "-Wno-old-for" does the same as "--dialect 0.94.8", and that will disable string symbols because they were introduced in release 0.97, much later. The "--dialect" switches are meant for assembling older sources and shouldn't really be used with new projects. Now obviously it would be possible to change the "support older versions" mechanism to enable things like combining "all the features of 0.98" with "use the ancient !for syntax" - but I would really prefer to keep...

Timo Taipalus posted a comment on ticket #21

Timo Taipalus — Fri, 30 Aug 2024 08:09:08 -0000

It seems to error if you assemble with "-Wno-old-for". !to "symboltest.prg", cbm !set mycolor = 7 *= $800 !macro will_be_expanded .color { lda #.color sta $d020 } !macro foo .tmp, .arg { ?(.arg) jmp * } +foo 0, "+will_be_expanded mycolor" rts Error - File acme-symboltest.acme, line 15 (Zone ): There's more than one character. Error - File acme-symboltest.acme, line 11 (Macro foo): Syntax error. Warning - File acme-symboltest.acme, line 15 (Zone ): ...called from here.

Marco Baye committed [r408] on Code

Marco Baye — Thu, 29 Aug 2024 21:02:25 -0000

added missing sanity check

Marco Baye committed [r407] on Code

Marco Baye — Thu, 29 Aug 2024 20:38:40 -0000

added code to tell "symbol already defined" (in this pass) and "symbol

Marco Baye committed [r406] on Code

Marco Baye — Thu, 29 Aug 2024 18:27:51 -0000

"symbol twice" error now outputs location of previous definition,

Marco Baye committed [r405] on Code

Marco Baye — Thu, 29 Aug 2024 15:14:13 -0000

refactored "macro twice" code. messages about initial definitions and macro

Marco Baye committed [r404] on Code

Marco Baye — Wed, 28 Aug 2024 16:45:32 -0000

refactored error/warning stuff

Marco Baye committed [r403] on Code

Marco Baye — Wed, 28 Aug 2024 13:12:07 -0000

refactored program counter / outbuffer stuff

Marco Baye committed [r402] on Code

Marco Baye — Tue, 27 Aug 2024 18:54:08 -0000

finally removed the 64 KiB limit, the outbuffer size is now determined at

Timo Taipalus posted a comment on ticket #24

Timo Taipalus — Wed, 21 Aug 2024 09:56:14 -0000

I agree on the syntax. Procedural in my opinion is crucial. Ideally we could have both, of course. I personally have several instances where somewhat complex calculations were needed for a single return value, in various places. This doesn't compress into an oneliner. Anything that does emit data or code should be disallowed, as well as modifying global variables.

Marco Baye committed [r401] on Code

Marco Baye — Wed, 21 Aug 2024 00:00:32 -0000

writing to output buffer now only happens in final pass

Dan Sanderson posted a comment on ticket #24

Dan Sanderson — Sun, 18 Aug 2024 23:13:09 -0000

Is there a use case for evaluating these functions procedurally? It seems like it would simplify things if they were purely functional. Functions can't sensibly emit code or data to the program, so it might help if the definition syntax made that clear. !func myfunc(.arg) = (.arg+10)/2 !byte myfunc(5), myfunc(6) PI = 3.14159 !func circarea(.r) = PI*r*r Sharing calling syntax with the built-in functions (is_number(), etc.) might also be beneficial.

Marco Baye committed [r400] on Code

Marco Baye — Sun, 18 Aug 2024 22:49:35 -0000

added "output pass", to ease adding of new features.

Marco Baye committed [r399] on Code

Marco Baye — Sun, 18 Aug 2024 17:23:25 -0000

rearranged struct, no change in functionality

Marco Baye committed [r398] on Code

Marco Baye — Fri, 16 Aug 2024 22:19:56 -0000

in future versions, program counter in pseudopc blocks no longer silently wraps around to zero

Timo Taipalus created ticket #24

Timo Taipalus — Fri, 16 Aug 2024 21:38:33 -0000

Functions

Timo Taipalus posted a comment on ticket #21

Timo Taipalus — Fri, 16 Aug 2024 21:35:54 -0000

Thanks, it seems to do what I was hoping for.

Marco Baye committed [r397] on Code

Marco Baye — Fri, 16 Aug 2024 21:19:03 -0000

renamed struct component, no change in functionality

Marco Baye posted a comment on ticket #2

Marco Baye — Fri, 16 Aug 2024 14:40:27 -0000

will be fixed in release 0.98 (it's already fixed, but because of backward compatibility, the old behavior is still used by default. you can test the new behavior using "--dialect future")

Marco Baye posted a comment on ticket #6

Marco Baye — Fri, 16 Aug 2024 14:35:12 -0000

should be fixed now