Amiga Assembly extension for Visual Studio Code

[Antiriad_UK]

New 0.18.1 binaries are working for me now. Thanks!

[prb28]

Originally Posted by Antiriad_UK

New 0.18.1 binaries are working for me now. Thanks!

Happy to hear that!

[hooverphonique]

Ok, thanks for the explanation - makes sense! :-)

I have a problem with the formatter and macros - if I call a macro with arguments, the formatter adjusts the columns weirdly, and worse, if there's more than one argument, the macro name is moved to column 1 and space is inserted between the commas and the arguments, which means it fails to assemble.

[prb28]

Originally Posted by hooverphonique

I have a problem with the formatter and macros - if I call a macro with arguments, the formatter adjusts the columns weirdly, and worse, if there's more than one argument, the macro name is moved to column 1 and space is inserted between the commas and the arguments, which means it fails to assemble.

Can you give me an example of macro and how would you like to be formatted ?

As a workaround you can format a text selection or add it to an included file.
You'll get into it but debug and macros doesn't deal always well...

[hooverphonique]

Originally Posted by prb28

Can you give me an example of macro and how would you like to be formatted ?

It seems the case where it is moved to column 1 and spaces are inserted is, if a macro argument is recognized as a mnemonic:

        macro         some_macro
        \1.b          \2,d0
        endm

some_label:
        some_macro    or,d1

If you format the line where some_macro is referenced, you'll see what I mean.

[prb28]

Originally Posted by hooverphonique

If you format the line where some_macro is referenced, you'll see what I mean.

Thanks, yes, I understand. I'll try to fix it quickly.

[prb28]

Originally Posted by hooverphonique

It seems the case where it is moved to column 1 and spaces are inserted is, if a macro argument is recognized as a mnemonic.

Could you please try this version : https://github.com/prb28/vscode-amig....18.2.vsix.zip

• Unzip it on your disk
• launch vscode
• type F1 to have
• the menu
• Chose 'Extensions: Install from VSIX...'
• select the vsix file

You were right the 'or' mnemonic was disturbing my parse.

[hooverphonique]

Originally Posted by prb28

Could you please try this version : https://github.com/prb28/vscode-amig....18.2.vsix.zip

Thanks! That seems to fix the problem

[prb28]

Originally Posted by hooverphonique

Thanks! That seems to fix the problem

Great !
I wait a couple of days to see if there is more bugs before releasing it.

[Hannibal]

I have now integrated this in with my current project, and it all works. It is increasing the joy of coding :-) A couple of things I discovered
1. Like multiple people I use a separate build system and .s-files can't compile directly. No problem, I just set "enabled": false for the amiga-assembly.vasm in settings.json. That works - except it still tells me that to "please configure VASM compiler in the workspace" - I agree it makes sense to show this when the configuration is missing (so users know they need to configure it), but it's mildly annoying that I can't make that message go away when I have configured it properly
2. I had a few problems with symbols loading, but not matching up properly. One time I accidentally had different sections named CODE and code, and that may have been part of the problem. However, I'm not sure if this is a real problem, because even after merging those sections, I still see symbol mismatch sometimes in some build configurations. I'll post if I find out more

[prb28]

Originally Posted by Hannibal

It is increasing the joy of coding :-)

It's the point !

Originally Posted by Hannibal

1. I agree it makes sense to show this when the configuration is missing (so users know they need to configure it), but it's mildly annoying that I can't make that message go away when I have configured it properly

I had the same questions when I did it. But it's useful for syntax error checking and it might be useful at least for that. That's why I left it.

That shouldn't make an error when it's well configured: can you send me the settings.json ?

Originally Posted by Hannibal

2. I had a few problems with symbols loading, but not matching up properly.

I saw that sometimes, but when I try to reproduce it.... It works ... So if you have a context to reproduce the bug please send it !

[Hannibal]

My config looks like this.

{
    "amiga-assembly.cstool": "buildtool\\cstool.exe",
    "amiga-assembly.vasm": {
        "enabled": false,
        "file": "buildtool\\vasmm68k_mot_win32.exe"
    }
}

I verified that if I set enabled to true, it actually performs the checking, so I know configuration is correct.
I believe it is due to the places you call mayCompile(), if it returns false, you show the error message - maybe split it up into 2, like this?

if(isConfigured()) {
    if(mayCompile()) {
         ...do the work...
    }
    else {
        resolve()
     }
}
else {
    reject(new Error("Please configure VASM compiler in the workspace"));
}

}

[prb28]

Ok I'll add some code to deal with it in next release.

[hooverphonique]

Maybe a bit OT, but is FS-UAE not treating the "hd0" directory as a harddrive?
It just puzzles me that from the FS-UAE windows appears, it takes around 8 secs for the 3.5" drive clicks to begin, then another 45+ secs for my 75Kb executable to load, which seems like a long time (A500 512K/512K config).

[prb28]

Originally Posted by hooverphonique

Maybe a bit OT, but is FS-UAE not treating the "hd0" directory as a harddrive?

What are your options in the .vscode/launch.json ?
You should have something like :

                 "--hard_drive_0=${workspaceFolder}/fs-uae/hd0"

If you use FS-UAE in another context maybe there is some other default options in your installation.

[hooverphonique]

Originally Posted by prb28

What are your options in the .vscode/launch.json ?
You should have something like :

                 "--hard_drive_0=${workspaceFolder}/fs-uae/hd0"

If you use FS-UAE in another context maybe there is some other default options in your installation.

Yes, my options are

            "options": [
                "--chip_memory=512",
                "--hard_drive_0=${workspaceFolder}/fs-uae/hd0",
                "--joystick_port_1=none",
                "--amiga_model=A500",
                "--slow_memory=512"
            ]

I don't have fs-uae installed or used otherwise.

[hooverphonique]

Originally Posted by hooverphonique

Maybe a bit OT, but is FS-UAE not treating the "hd0" directory as a harddrive?
It just puzzles me that from the FS-UAE windows appears, it takes around 8 secs for the 3.5" drive clicks to begin, then another 45+ secs for my 75Kb executable to load, which seems like a long time (A500 512K/512K config).

Ok, I was wrong. I took the vasm output as gospel:

code(acrx2):            1210 bytes
data(acrx1):           71762 bytes
data_c(adrw1):            96 bytes
bss_c(aurw1):          30720 bytes

But it turns out that my output executable is 362kB due to the vasm "-linedebug" option. I guess I need to find a way to disable debug symbol generation for data sections, because it bloats the executable and is probably not really useful.

[Spec-Chum]

Quick question, but I fear this may be more difficult than it sounds, but when displaying the hover info for hardware registers, would it be possible to add the address?

Like:

To show

$100 - Bit Plane Control Register 0

or

$dff100 - Bit Plane Control Register 0

[prb28]

Originally Posted by hooverphonique

I guess I need to find a way to disable debug symbol generation for data sections, because it bloats the executable and is probably not really useful.

This is a question for @phx . I don't know how it can be done.

[prb28]

Originally Posted by Spec-Chum

Quick question, but I fear this may be more difficult than it sounds, but when displaying the hover info for hardware registers, would it be possible to add the address?

Can you please add a feature request on Github?
All the docs are in markdown files, it should be easily done.