Amiga GCC 8.3+gdb extension for Visual Studio Code

[Spec-Chum]

Originally Posted by deimos

I've not touched anything yet, so my makefile looks like:

CCFLAGS = -g -MP -MMD -m68000 -O1 -nostdlib -Wall -Wno-pointer-sign -Wno-unused-function -Wno-volatile-register-var -Wno-discarded-qualifiers -fomit-frame-pointer -fno-tree-loop-distribution -flto -fwhole-program

I will try to change that and hopefully reproduce your problem.

EDIT:

Yes, problem confirmed with the default of:

CCFLAGS = -g -MP -MMD -m68000 -Ofast -nostdlib -Wall -Wno-pointer-sign -Wno-unused-function -Wno-volatile-register-var -Wno-discarded-qualifiers -fomit-frame-pointer -fno-tree-loop-distribution -flto -fwhole-program

The sprite doesn't move.

Thanks for confirming, can you just put volatile on the spr[1]++ cast at all?

I'm at work, so can't check

[deimos]

And it looks like your diagnosis is correct:

((/* important */ volatile /* here */ UBYTE *)spr)[1]++;

[Spec-Chum]

Originally Posted by deimos

And it looks like your diagnosis is correct:

((/* important */ volatile /* here */ UBYTE *)spr)[1]++;

Awesome, thanks for checking

[Spec-Chum]

Originally Posted by deimos

And it looks like your diagnosis is correct:

((/* important */ volatile /* here */ UBYTE *)spr)[1]++;

Home now, confirmed working again with -Ofast, hooray!

Thanks again for checking, much appreciated!

[Tom_Goblins]

Please can you confirm if it works for c++?, I saw a comment before but It wasn't clear enough.

I am trying to find my environment to code on c++ but now I am missing a nice debugger and this could be a great solution. I have been using Bebbo's gdbserver, printf!!, tons of them XD.

Thanks!

[asymetrix]

I got the addon to work but could not figure out how to include standard C/C++ headers - I could not follow an Amiga C book nor a standard windows C book.
Amiga really hinders my programming experience.

[deimos]

Originally Posted by asymetrix

I got the addon to work but could not figure out how to include standard C/C++ headers - I could not follow an Amiga C book nor a standard windows C book.

That's not what it's for. It's not a full C++ environment with all those libraries. It's a cut down pure Amiga environment for demo / game creators.

[roondar]

I've recently found this rather useful extension. It works well, but I have run into a small problem.

Debugging only seems to work once.

That is, I can debug to my hearts content, until I stop debugging. When I use the Stop Debugging command from VS Code (prior to the program itself ending), this does stop the debugger. But after that I can't get it to start again. I have to restart Visual Studio Code for it to work once more.

Does anyone here know how to fix this?

[thyslo]

For debugging I'm building the object files like

/opt/amiga/bin/m68k-amigaos-c++ -fno-rtti -fno-exceptions -noixemul -O0 -g -Wl,--amiga-debug-hunk -ldebug -c -o file.o file.cpp

Then I link them all using the silimar call

/opt/amiga/bin/m68k-amigaos-c++ -fno-rtti -fno-exceptions -noixemul -O0 -g -Wl,--amiga-debug-hunk -ldebug -o Application *.o

When debugging the stepping through the code works. But all variables are displayed with wrong / random values. These values don't change when stepping over a line where such a variable is set.

Is there something obviously wrong with my gcc/c++ options?

[Bartman]

Update: new version 0.8.1 released, supports C++ now
Download Github

[deimos]

Originally Posted by Bartman

Update: new version 0.8.1 released, supports C++ now
Download Github

Nice. Thank you.

[coldacid]

@Bartman

Any chance you might get this added to the VS Marketplace?

[Bartman]

Updated. New version 0.9.0 features GCC 10.1, binutils 2.34, GDB 9.1
Download GitHub
should improve code performance a bit.

[deimos]

Originally Posted by Bartman

Updated. New version 0.9.0 features GCC 10.1, binutils 2.34, GDB 9.1
Download GitHub
should improve code performance a bit.

But GCC 10.1 is only 4 days old!

[coldacid]

Originally Posted by Bartman

Updated. New version 0.9.0 features GCC 10.1, binutils 2.34, GDB 9.1

This thing's HUGE for A VSCode extension! Did you include all those in it?

[Bartman]

Originally Posted by coldacid

This thing's HUGE for A VSCode extension! Did you include all those in it?

Yes!

[Bartman]

Hey guys,
I just released version 1.0.0 on the Visual Studio Code Marketplace.

This is probably the biggest update ever.

excerpts from CHANGELOG for 1.0.0:

• added function-level + DMA profiling: during a debugging session, press the Profile button on the right of the debug toolbar, and 1 frame will be profiled.
• added ELF file size profiling: right-click an ELF file in the explorer, and select Amiga: Profile File Size
• added WinUAE debug overlays. See template project for debug_* function calls for an example
• updated to latest 64-bit WinUAE
• added command Amiga: Open Terminal
• improved INCBIN macro to correctly report binary size to the size profiler.
• added INCBIN_CHIP macro to put binaries directly into chip mem.
• better demo project, shows copper, bitplanes
• support for different Amiga models (A500, A1200, A4000) in .vscode/launch.json
• now available in the Visual Studio Code Marketplace

Here are some screenshots for ya.

[korruptor]

Thank you! I've been using it for a couple of weeks, from your github, and it's insanely cool. Thank you for sharing all your hard work.

[Antiriad_UK]

Hi,

I've got an external assembler file with an exported function, e.g just takes d0 as input and moves to d1 then returns.

  xdef MyFunction
MyFunction:
  move.l d0,d1
  rts

Assembled to elf object format with:
vasmm68k_mot.exe -m68000 -Felf

How do I write a C header prototype that can call that function. Tried every example for gcc 6 and they all give errors. It's going to be something like
void MyFunction(register const void* input __asm("d0"));

But it doesn't like __asm.

In the example project with the compiler there's a wrapper around p61 player. It looks like a custom version of p61 has been created and then a jump table has been implemented at the start. So then the C is :

void p61Music() {
	volatile register const void* _a3 __asm("a3") = player;
	volatile register const void* _a6 __asm("a6") = (void*)0xdff000;
	__asm volatile (
		"movem.l %%d0-%%d7/%%a0-%%a2/%%a4-%%a5,-(%%sp)\n"
		"jsr 4(%%a3)\n"
		"movem.l (%%sp)+,%%d0-%%d7/%%a0-%%a2/%%a4-%%a5"
	: "+rf"(_a3), "+rf"(_a6)
	:
	: "cc", "memory");
}

I could totally implement my own jumptable and then copy this idea, but is there really no way to do it directly from a prototype to an exported function? Also where is this documented - I can guess the idea but where is "+rf" and "cc" "memory" documented for m68k? Or is it part of bartman's port?

Thanks, driving me nuts

Edit: I got the jump table version working but would be nice to know if there's an alternative.

[deimos]

Originally Posted by Antiriad_UK

How do I write a C header prototype that can call that function. Tried every example for gcc 6 and they all give errors. It's going to be something like
void MyFunction(register const void* input __asm("d0"));

But it doesn't like __asm.

This is how I do it:

void ClipAndFillPolygon2D(const UWORD n, const Point2D * polygon, const UWORD colour) {
    WaitForBlitter();

    {
        register APTR * _a0 asm("a0") = display.backBufferBitplanes;
        register UWORD _d0 asm("d0") = n;
        register Point2D * _a1 asm("a1") = polygon;
        register UWORD _d1 asm("d1") = colour;

        asm volatile (
            "        jsr     _scanlineFill"
            : // no outputs
            : "r" (_d0), "r" (_d1), "r" (_a0), "r" (_a1) // inputs
            : "memory" // changes memory
        );
    }
}

This is where it's documented: https://gcc.gnu.org/onlinedocs/gcc/Extended-Asm.html

Function prototypes with parameters mapped to registers is not supported, but you can map variables to registers, so you need to write a little bit of wrapper code like this. The supplied library code wrappers by bartman use macros for this and are probably also worth a look.

The gcc assembly syntax is unpleasant, so you probably don't want to use it for much more than wrapping a function.

The

"cc", "memory"

bit says that the assembly code will clobber the condition code register and memory, so disable any optimisations that depend on them. You can specify individual registers that get clobbered as well, which may allow for smarter optimisations.