tools.nes/lib/xixanta/src/node.rs, branch main

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à

Add global labels

2026-08-18T14:39:37Z

These are labels that are declared by prefixing a '#' symbol to the name, and it allows the label to be declared at the global scope instead of the current one. This is a feature which is not to be abused so to not make scopes pointless, but it can be quite handy with some optimizations while not abandoning scopes completely. Signed-off-by: Miquel Sabaté Solà

Add support for the asan:fixed-segments comment

2026-07-09T20:14:22Z

This magic comment allows for the definition of segments that are fixed and for which references are always safe. This goes in tandem with the asan:safe comment, which can then be used more sporadically. Signed-off-by: Miquel Sabaté Solà

Add a warning for unknown cross-mapping references

2026-07-08T19:27:49Z

Some segments, like the 'vectors' one, will reference code that is outside of its mapping. But in some other configurations, segments cannot make these cross-mapping references so happily. Imagine: .segment "SWAPPABLE" .proc foo rts .endproc .segment "FIXED" jsr foo Here the assembler will properly detect the address of 'foo' in the context of the 'SWAPPABLE' segment. But what this assembler doesn't know is that this segment is swappable (e.g. UNROM chip). Hence, if the bank being mapped right now is not the one containing the 'SWAPPABLE' segment, then the address computed for 'foo' and used in that 'jsr' instruction will point to something else entirely. This would be similar to a use-after-free bug. This is something that can only be inspected at runtime, and so the assembler cannot be of much help here. Hence, this commit adds a warning so the programmer can understand the potentially dangerous operation. All of that being said, this commit also adds support for "asan:safe" or "check:safe", which is a magic comment that the programmer can write to re-assure the assembler that this operation is fine (e.g. there is a guarantee that the mapped bank is that one we are expecting). Hence, the code above could now be written like so: jsr foo ; check:safe Signed-off-by: Miquel Sabaté Solà

Add the .min and the .max control expressions

2026-04-24T21:12:51Z

Signed-off-by: Miquel Sabaté Solà

Add a big endian control statement

2026-04-24T20:29:47Z

By default everything is little endian, and that should always be the case. That being said, if a literal is better expressed in big endian format for whatever reason, you can now use the .be or the .bigendian control statements. The terribly named .dbyt control statement can also be used for this purpose, but that's just to be compatible with the implementation from ca65. Signed-off-by: Miquel Sabaté Solà

Add the .version pseudo-variable

2026-04-24T14:26:08Z

Signed-off-by: Miquel Sabaté Solà

Implement the asan:stack statement

2026-04-08T14:04:12Z

This statement allows programmers to reserve a memory range for the stack. This is useful to reserve a memory region which is not attached to any variable, and: 1. It is a way to safely reserve space on the $0100 page. 2. The --stats/--write-info flags will be able to add up the memory space reserved for the stack. 3. Future tooling might be able to use this value as a way to detect stack overflows. Signed-off-by: Miquel Sabaté Solà

Ensure fallthrough is not considered a valid identifier

2026-02-03T09:49:10Z

Signed-off-by: Miquel Sabaté Solà

Change .fallthrough to fallthrough

2026-02-02T22:22:47Z

Implementing it as a control statement has the bad thing that it's impossible to be compatible with other assemblers such as ca65, as you cannot create dummy control statements or something like that in there. Instead of that, we define it with the special underscores which are still valid for identifiers, and give a "compiler-specific thingie" flair to it. This also has the benefit that the parser can be a bit more strict. Signed-off-by: Miquel Sabaté Solà

tools.nes/lib/xixanta/src/node.rs, branch main

Do not mark some valid identifiers as invalid

Add global labels

Add support for the asan:fixed-segments comment

Add a warning for unknown cross-mapping references

Add the .min and the .max control expressions

Add a big endian control statement

Add the .version pseudo-variable

Implement the asan:stack statement

Ensure __fallthrough__ is not considered a valid identifier

Change .fallthrough to __fallthrough__

Ensure fallthrough is not considered a valid identifier

Change .fallthrough to fallthrough