tools.nes, branch main

Stop execution if not active in until_address()

2026-08-25T05:36:54Z

Even if the desired thing is to run until the provided address is reached, abort execution as well if the machine stops being active as well. This is a common scenario when running in function mode and the target end address is something passed that. Fixes: e6c41303c2da ("runrom: add the --until-address option") Signed-off-by: Miquel Sabaté Solà

Add a couple of notes on contributing

2026-08-25T05:07:25Z

Signed-off-by: Miquel Sabaté Solà

runrom: add the --until-address option

2026-08-24T14:18:27Z

This allows the user to run execution until a given address is reached. This can, like with the --start option, be coupled with the --nasm option in order to be able to provide an identifier instead of a regular hexadecimal value. Signed-off-by: Miquel Sabaté Solà

Allow the --start flag to accept identifiers

2026-08-24T14:17:25Z

This is coupled with the new -n/--nasm option, which works in the same way as in `readrom`. Signed-off-by: Miquel Sabaté Solà

Annotate the no-return from die()

2026-08-24T12:16:42Z

In all crates we are using a die() function to print to stderr and quit with a exit status > 0. Apparently in Rust you can annotate the return type with a bang just like the noreturn from the C family. The added bonus is that some useless statements to make the compiler happy without it can be removed altogether as now the compiler is able to understand that it won't return so the returned type is not needed. Signed-off-by: Miquel Sabaté Solà

nasm: provide a better layout for the README file

2026-08-23T21:15:27Z

Signed-off-by: Miquel Sabaté Solà

Improve the description of runrom

2026-08-23T21:15:08Z

Signed-off-by: Miquel Sabaté Solà

nasm: fix typo on the README

2026-08-18T14:53:17Z

Signed-off-by: Miquel Sabaté Solà

Do not mark some valid identifiers as invalid

2026-08-18T14:44:27Z

Some identifiers like "@aa" were marked as invalid as "aa" is a potentially hexadecimal value, but the "@" symbol actually disambiguates this situation. Hence, if a non-alphanumeric character (that the parser liked) is actually found, ensure it cannot be considered as an hexadecimal value. Provide also a test of is_valid_identifier(). The list is certainly not exhaustive, but it should be good enough coupled with end-to-end tests. Signed-off-by: Miquel Sabaté Solà

Validate labels when walking through the context

2026-08-18T14:41:34Z

The parser does not validate label names completely (it only takes care of validating that it something that makes sense syntactically). The assembler can tell whether the label is actually taking a reserved name, or an invalid hexadecimal constant, etc. Before this commit a user would get a cryptic "invalid identifier" message when referencing an invalid label (e.g. "jmp 1234"). Fix this by validating the identifier there, but also when the label was defined before any of this. Signed-off-by: Miquel Sabaté Solà