Вид для печати
Для этих макросов, вроде в Сжасме есть готовые директивы.
Первый (DUPL), как я понял, просто заполняет LEN байт памяти байтом FILL.
Для этого есть BLOCK <length>[,<fill byte>] (DEFS <length>[,<fill byte>]).
Второе это старший/младший байты.
В Сжасме они есть тоже.
Цитата:
low low x low 8 bits of 16 bit value or lower part of register pair
high high x high 8 bits of 16 bit value or higher part of register pair
Не могу понять, как правильно работать с IFUSED?
Главная программа.Цитата:
DEVICE ZXSPECTRUM48
ORG 0x8000
main:
<code>
<code>
<code>
<code>
<code>
ret
include "address.asm" ; здесь объявлен модуль coords
include "out43.asm"
include "sto_rec.asm"
include "pause.asm"
include "windows.asm"
Файл address.asm, в котором объявлен модуль coords.Цитата:
module coords
ifused XxXxXxX
XxXxXxX <code>
<code>
<code>
<code>
ret
endif
Другой модуль, который ссылается на ссылку в модуле coords.Цитата:
module windows
CLS <code>
<code>
<code>
<code>
<code>
call coords.XxXxXxX
ret
Результат...Цитата:
Pass 3 complete
Errors: 4, warnings: 0, compiled: 870 lines, work time: 0.015 seconds
The terminal process "C:\Program Files\PowerShell\7\pwsh.exe -Command sjasmplus --sld=test.sld --fullpath test.asm" terminated with exit code: 1.
Terminal will be reused by tasks, press any key to close it.
> Executing task: sjasmplus --sld=test.sld --fullpath test.asm <
SjASMPlus Z80 Cross-Assembler v1.18.2 (https://github.com/z00m128/sjasmplus)
Pass 1 complete (0 errors)
Pass 2 complete (0 errors)
windows.asm(91): error: Label not found: windows.coords.XxXxXxX
Что неправильно?
upd
"Known bug: when code is using label inside module "moduleX", like call labelY, only usage of moduleX.labelY label is noted. Then if you define "labelY" outside of module and hide it inside IFUSED labelY block, the call from module will be unable to find the routine.
Workaround: you can use the global-label operator @: "call @labelY" to trigger usage of the global "labelY", or you can use the alternative IFUSED syntax "labelY: IFUSED" which does not only check condition, but also does define the label. Once the label is defined, the "call labelY" line inside module will find the global variant and mark it as "used" correctly."
Оно?
Вроде бы, оно...
Но новая беда - если написать
labelY: IFUSED
то не работают временные метки. :(
Так работает, а с новым синтаксисом да, косяк.Код:module n1
call @m1.used1
endmodule
module m1
ifused used1
used1
nop
jr 1F
nop
1
ret
endif
endmodule
Ну, у меня с @ не работает.
Цитата:
Pass 1 complete (0 errors)
Pass 2 complete (0 errors)
address.asm(25): error: [JR] Target out of range (+598)
address.asm(29): error: Local-labels flow differs in this pass (missing/new local label or final pass source difference)
address.asm(33): error: Local label not found: 4F
address.asm(36): error: Local-labels flow differs in this pass (missing/new local label or final pass source difference)
out43.asm(28): error: [JR] Target out of range (+434)
out43.asm(32): error: Local-labels flow differs in this pass (missing/new local label or final pass source difference)
windows.asm(18): error: Local-labels flow differs in this pass (missing/new local label or final pass source difference)
include data: name=font.fnt (768 bytes) Offset=0 Len=768
Pass 3 complete
Errors: 7, warnings: 0, compiled: 927 lines, work time: 0.031 seconds
The terminal process "C:\Program Files\PowerShell\7\pwsh.exe -Command sjasmplus --sld=test.sld --fullpath test.asm" terminated with exit code: 1.
Не бывает у меня работает, у других нет. Значит ошибка в другом. Скорее всего ifused объявлен до использования, это в любом случае ошибка.Цитата:
Сообщение от 0xDEAD
- - - Добавлено - - -
Хотя я проверял без инклюдов. В сиджасме они как выяснилось влияют не на совсем очевидные вещи.
Подпрограммы, которые я хочу использовать с ifused у меня в include лежат, которые размещены после ret главной программы. К меткам, которые объявлены в том модуле, который я хочу пометить как ifused, в любом случае, обращение происходит раньше по тексту программы, если это имеется в виду.
К тому же, непонятна связь между объявлением ifused и моментальной сразу же после этого потерей работоспособности временных меток.
Цитата:
address.asm(33): error: Local label not found: 4F
Интересно, на какие, например?Цитата:
Сообщение от krt17
Да это. Но то что вы написали в первом посту говорит о другом. Проверил с инклюдами, все в порядке.
Сделайте минимальный синтетический тест, будет попонятнее.
- - - Добавлено - - -
В старом обсуждении параллельной ветки был мой пример. Насколько я помню в этой ветке его вылечили, но помню я плохо, посему будем считать что проблем с инклюдом и ифюзед уже нет.Цитата:
Сообщение от 0xDEAD
В официальной документации к компилятору прямым текстом написано, что есть баг. С ifused. Про include, правда, там речь не идёт.Цитата:
Сообщение от krt17
Да написано. Прочитали? Предложено пара воркараундов, один работает, во втором проблема с временными метками.
тест обеих случаев, Ped7g посмотрит разберется
Код:device zxspectrum48
org 0x8000
start
module n1
call @m1.used1
call m2.used2
jr $
endmodule
module m1
ifused used1
used1
nop
jr 1F
nop
1
ret
endif
endmodule
module m2
used2: ifused
nop
jr 2F
nop
2
ret
endif
endmodule
savesna "usedtest.sna", start
the temporary number-labels may not work inside IFUSED, if the first pass doesn't already detect the label as used...
I did rewrite temporary label implementation in v1.11.1 I think? As it was not working correctly when amount of lines did change between passes, but thinking about it (not 100% sure), maybe now they don't mind changing amount of lines, but require to form the same list across all passes, so if some of them are missing because of IFUSED in first pass was false, then true later, the total list is different, and it maybe fails because of that.
If you have only few of them, consider to change them to local labels? Or include the libraries after the main code, when the IFUSED will already know in first pass, which routines are used?
Of course it would be better to fix sjasmplus, but that may take some time, or somebody else doing it, right now I'm waiting for z00m to release 1.18.3, not planning to work on sjasmplus this +-year.
Still, if you can produce some minimal failing example, it may help to target the bug easier.
About calling from one module to other ... the `call @other_module.function` is IMO best way, as that's what the source is really doing. Without "@" the label `my_module.other_module.function` is first-priority and other variants are searched only if that fails. Which usually still works for almost anything, except IFUSED. But I don't consider this 100% bug on sjasmplus side, it's heuristic, if you don't specify full global name, and as any heuristic - it's not perfect. (and there's no 100% correct fix for it, whatever you do, you can create anti-example where the new method will fail, as the whole concept is ambiguous).
... or you can try to zip your project and send it to me to see if I can quickly patch it to assemble with latest version (would be probably quicker to patch your sources, than sjasmplus... :D ...and maybe not).
- - - Updated - - -
ah, you (krt17 - thank you) did produce the minimal example. And seems I remember it correctly, the heuristic guessing what label you want to call at `call m2.used2` fails as the `n1.m2.used2` is first-priority in first pass, then the `used2: ifused` in first pass is "false", which makes the "2" temporary label non-existent in first pass.
You can fix such source either by being more explicit in the call using "@" to target the correct module `call @m2.used2`, or you can change the "2" temporary label to some local label. Using those number-labels inside IFUSED blocks is really bad idea since v1.11.1 ... and using them before is really bad idea too... Hmm... I guess it's just bad idea in any case. Use regular labels. :)
edit2: but I guess the temporary labels stuff is more like bug... maybe it could accept changes to the temporary labels list between first and second pass, but I'm not sure if that is enough to resolve this. I will keep that example around and maybe check it later, what can be done about it. 0xDEAD: anyway, thank you for reporting your issue, and sorry I don't have some perfect fix for you.