what i did was exporting a symbol in one C file, using pragmas to make it a zeropage symbol and also pushing it into a custom segment. and then i import it in another file, again using pragma to make it a zeropage symbol (as described in the docs):
extern char foo;
#pragma zpsym ("foo")
int n;
int main(void) {
n = foo;
return 0;
}//#pragma bss-name (push,"ZEROPAGE") /* no warning */
#pragma bss-name (push,"MYZEROPAGE") /* warning */
char foo;
#pragma zpsym ("foo")
#pragma bss-name (pop)now the odd thing is, the assembler gives this warning:
zpsym2.s(18): Warning: Symbol `foo' is absolute but exported zeropage
...which seems wrong (and is a bit irritating). also the generated code is correct (uses zeropage adressing).
whats interesting is that the warning goes away when putting the symbol into the regular "ZEROPAGE" segment (without changing anything else) - that seems to imply that its actually a bug, because for extra zeropage variables using an extra segment is pretty much required.
what i did was exporting a symbol in one C file, using pragmas to make it a zeropage symbol and also pushing it into a custom segment. and then i import it in another file, again using pragma to make it a zeropage symbol (as described in the docs):
now the odd thing is, the assembler gives this warning:
...which seems wrong (and is a bit irritating). also the generated code is correct (uses zeropage adressing).
whats interesting is that the warning goes away when putting the symbol into the regular "ZEROPAGE" segment (without changing anything else) - that seems to imply that its actually a bug, because for extra zeropage variables using an extra segment is pretty much required.