VASM errors : how to fix them?

[kamelito]

@PHX,
I've resourced a prg and I got the following errors :

vasm -m68060 -m68851 -no-opt -devpac -Fhunkexe -kick1hunks prog.asm

error 9 in line 2824 of "prog.asm": instruction not supported on selected architecture
> PMOVE.L TT0,(8,A0)

error 9 in line 2825 of "prog.asm": instruction not supported on selected architecture
> PMOVE.L TT1,(12,A0)

error 1 in line 2834 of "prog.asm": illegal operand types
> MOVEC MMUSR,D0

error 1 in line 2837 of "prog.asm": illegal operand types
> MOVEC TC,D0

error 1 in line 2839 of "prog.asm": illegal operand types
> MOVEC ITT0,D0

What am I doing wrong?
thx

[jotd]

vasm 1.8k here, I don't have any issues with

MOVEC TC,D0

MOVEC ITT0,D0

provided I set MC68060 in the asm code

I can also do

MOVEC DTT0,d0

(not TT0, and not into memory, use a register first)

MMUSR is probably not the real name of the register for vasm.

[kamelito]

Originally Posted by jotd

vasm 1.8k here, I don't have any issues with

MOVEC TC,D0

MOVEC ITT0,D0

provided I set MC68060 in the asm code

I can also do

MOVEC DTT0,d0

(not TT0, and not into memory, use a register first)

MMUSR is probably not the real name of the register for vasm.

Like this?
machine mc68060
I thought that passing the MC68060 via the command line was sufficient.

[meynaf]

Dunno for vasm, but for phxass the following will assemble without errors :

 mc68030
 pmove.l tt0,(8,a0)
 pmove.l tt1,(12,a0)
 mc68040
 movec mmusr,d0
 movec tc,d0
 movec itt0,d0

[phx]

Originally Posted by kamelito

vasm -m68060 -m68851 -no-opt -devpac -Fhunkexe -kick1hunks prog.asm

error 9 in line 2824 of "prog.asm": instruction not supported on selected architecture
> PMOVE.L TT0,(8,A0)

PMOVE from/to TTx registers is 68030 only.

error 1 in line 2834 of "prog.asm": illegal operand types
> MOVEC MMUSR,D0

MOVEC with MMUSR is 68040 only.

error 1 in line 2837 of "prog.asm": illegal operand types
> MOVEC TC,D0

error 1 in line 2839 of "prog.asm": illegal operand types
> MOVEC ITT0,D0

And these are 68040/68060 only.
I don't get the last errors, as you selected -m68060. Maybe a bug in your vasm version, which was fixed later?

To assemble all these instructions you would have to enable 68030 and 68040 together, which only works by

-m68020up

. Although, I would recommend to select the appropriate CPU in the source as there are ambiguities between these models, like PFLUSHA.

[kamelito]

@phx
-m68020up worked, I still have other errors due to resource badly disassembly some instructions.
I guess those instructions should be put in dc.x to be able to run on 68000 Amigas like the original program does.
Thanks to all for your help.

Is there an option to assemble code with new syntax or is it done automatically because I've errors like this : ) expected > LEA (pc.MSG,PC),A0

PS I was using version j but upgraded to k build by someone and put to grandis.

[Thomas Richter]

Actually, none of these instructions will work on the 68000.

[phx]

Originally Posted by kamelito

Is there an option to assemble code with new syntax or is it done automatically because I've errors like this : ) expected > LEA (pc.MSG,PC),A0

New and old syntax can be mixed. vasm reads both.
The problem here is that the register parser stops at the '.' and thinks it is a PC register. Even with -ldots or -devpac, which should allow dots in labels. I guess I have to fix that.

[kamelito]

Originally Posted by Thomas Richter

Actually, none of these instructions will work on the 68000.

I know that why I wrote about using dc.x instead, I think it is used to be executed if the CPU needed is present.

[kamelito]

Originally Posted by phx

I guess I have to fix that.

[roondar]

On the topic of CPU specific code, it might be worth pointing out you can also use a VASM directive for that in your code.

   mc68010 ; Now 68010 instructions are recognised
   <<awesome 68010 code>>
   mc68040 ; Now 68040 instructions are recognised
   <<even better 68040 code>>
   mc68000 ; Back to 68000 only code

I found that to be quite useful.
Edit: just saw meynaf pointed this out for phxass already.

[phx]

Originally Posted by phx

The problem here is that the register parser stops at the '.' and thinks it is a PC register. Even with -ldots or -devpac, which should allow dots in labels. I guess I have to fix that.

Done. You can try tomorrow's source snapshot at http://sun.hasenbraten.de/vasm/index.php?view=source

Although I don't like dots in labels or symbols, which is why vasm doesn't support it in default mode. It's confusing while parsing and reading such a source, because a '.' very much looks like a separator.

[kamelito]

Thanks, I‘ll try that.

[kamelito]

@PHX
Just build the snapshot 28 Apr 2021 02:13:57 GMT: vasm.tar.gz (482247 bytes) and with the -devpac I've no more the errors I had.
thanks!