GCC 6.2 toolchain for AmigaOS 3

[bebbo]

Originally Posted by meeku

Hi, I've followed the guide to get eclipse/bgdbserver up and running.. It all worked up until trying to actually debug where I get an error from bgdbserver (on winUAE and echoed to Eclipse) saying:
failed to load program /test/hello-world;exit

Any ideas?

please check:

• was hello-world copied into the folder '...../test'? (check post build command in Eclipse)
• is bgdbserver located in the folder '...../test'?
• was bgdbserver started with current dir '...../test'?

On the Amiga '/test/hello-world;exit' means: bgdbserver removes the trailing ';exit' and searches parent dir -> folder named 'test' -> program named 'hello-world'.

[meeku]

Originally Posted by bebbo

please check:

• was hello-world copied into the folder '...../test'? (check post build command in Eclipse)
• is bgdbserver located in the folder '...../test'?
• was bgdbserver started with current dir '...../test'?

On the Amiga '/test/hello-world;exit' means: bgdbserver removes the trailing ';exit' and searches parent dir -> folder named 'test' -> program named 'hello-world'.

Post build command in Eclipse is definitely copying the build output into /test on the Amiga. If I delete the file and re-build it's back where it should be.
bgdbserver is located in dh1:test
hello-world is located in dh1:test
bgdbserver is started in the /test folder with -r
The test folder is visible on both the PC and inside winuae
It all looks as it should!

[meeku]

I've also tried starting bgdbserver -r as
dh1:test/bgdbserver -r (using full path)

[jamie]

Hello all,

I used one of the first version of gcc 6(thanks Bebbo) and i updated to the last version (installer 20190306), in my code i redefined the operator new and delete and now i have this error "multiple definition of `operator new(unsigned int); /Users/fmacr/AppData/Local/Temp/ccxeiJBZ.o:/Users/fmacr/AppData/Local/Temp/ccxeiJBZ.o.text+0x8464): first defined here"

Do you know how to fix this error? Thanks

[jamie]

My mistake, my functions were in a .h but not inlined.

[BastyCDGS]

Regarding the low size startup code:

By using OldOpenLibrary instead of OpenLibrary for opening dos.library one moveq #33,d0 (i.e. 2 bytes more) is saved.

If we don't care about return code of OpenLib call, we actually can open any library version.

[Toni Wilen]

I am probably missing something obvious but I can't get attached program (source + binary included) to run under KS 1.3. (It runs fine if KS 2.0+). Or am I expecting something that is not yet implemented?

Something in startup code tries to execute JSR (A6,-$02ac) = AllocVec, before main() gets called.

This program needs to run under KS 1.3 + 68000 for obvious reasons (loads A500 UAE state files. "Official" release will happen when it runs under KS 1.3, don't ask anything yet..)

I usually write these kinds of programs in assembly but this time I tried to write almost everything in C and only small critical bits in assembly.

[bebbo]

Originally Posted by Toni Wilen

I am probably missing something obvious but I can't get attached program (source + binary included) to run under KS 1.3. (It runs fine if KS 2.0+). Or am I expecting something that is not yet implemented?

Something in startup code tries to execute JSR (A6,-$02ac) = AllocVec, before main() gets called.

Guess you got caught by a recent bug: I killed somehow the "-mcrt=nix13" flag for nix13 builds, so the AllocVec replacement was neither built nor used.

But it's fixed already.

update, rinse and repeat?

I'll look into it too.

[alkis]

Originally Posted by Toni Wilen

I am probably missing something obvious but I can't get attached program (source + binary included) to run under KS 1.3. (It runs fine if KS 2.0+). Or am I expecting something that is not yet implemented?

Something in startup code tries to execute JSR (A6,-$02ac) = AllocVec, before main() gets called.

This program needs to run under KS 1.3 + 68000 for obvious reasons (loads A500 UAE state files. "Official" release will happen when it runs under KS 1.3, don't ask anything yet..)

I usually write these kinds of programs in assembly but this time I tried to write almost everything in C and only small critical bits in assembly.

¨
Your toolchain needs update. With a version git-pulled/make update/make on 2/5, I get a running executable on (emulated) A1000.

Displays "Statefile parameter missing." when run.

[Toni Wilen]

Thanks. I knew I missed something obvious, it works now. I did update few days ago but didn't notice there was even more recent changes.

[ShK]

Does this compile for you with -lnix13 LIBS?

https://github.com/tonioni/pfsdoctor

[bebbo]

Originally Posted by ShK

Does this compile for you with -lnix13 LIBS?

https://github.com/tonioni/pfsdoctor

no - it needs asl.library

[arti]

Bebbo, prebuilt windows toolchain not updated anymore ?

EDIT: Updated, thanks

[Toni Wilen]

ndk13-include/inline/expansion.h has only one function (AddConfigDev). Manual copy from ndk-include worked as a workaround (I needed FindConfigDev which exists in KS 1.3).

[wawa]

@bebbo
im trying to get scalos compile with your gcc, but a type is missing from stdlib header, as it seems:

/home/wawa/opt/amiga/m68k-amigaos/sys-include/stdlib.h:108:64: error: unknown type name '_mbstate_t'
__stdargs int _mblen_r (struct _reent *, const char* , size_t, _mbstate_t *);

[alkis]

grep -R _mbstate_t /opt/amiga/ (or wherever you installed the compiler) shows up a few places.

wchar.h looks most promising. Maybe try #include <wchar.h> prior to stdlib.h?

[Toni Wilen]

How is it possible to have 68020, 68030 and 68040/060 specific instructions in same assembly file?

https://github.com/tonioni/ussload/blob/master/asm.S and uncomment PMOVEs at the end. How to compile this without ugly dc.w <opcode> workarounds?

For example "MOVEC D0,CAAR" is 68020/68030 only, "PMOVE (SP),TC" is 68030 only and "MOVEC D0,URP" is 68040/060 only.

(Thanks for fixing ndk1.3 expansion.library )

[pipper]

there’s the ‚mc680x0‘ directive. Would it be possible to sprinkle multiple of them into the right places?

[bebbo]

Originally Posted by Toni Wilen

How is it possible to have 68020, 68030 and 68040/060 specific instructions in same assembly file?

https://github.com/tonioni/ussload/blob/master/asm.S and uncomment PMOVEs at the end. How to compile this without ugly dc.w <opcode> workarounds?

For example "MOVEC D0,CAAR" is 68020/68030 only, "PMOVE (SP),TC" is 68030 only and "MOVEC D0,URP" is 68040/060 only.

(Thanks for fixing ndk1.3 expansion.library )

I modified the .arch directive locally in m68k-amigaos-as to be used multiple times... so this would work:

        | switch to 68040
        .arch 68040
        movec d0,urp
        .arch   68020
        movec d0,caar
        .arch 68030
        pmove (sp),tc
        .arch 68000
        | back to 68000

and really yields:

   0:   4e7b 0806       movec d0,urp
   4:   4e7b 0802       movec d0,caar
   8:   f017 4000       pmove (sp),tc

If you want it, I'll put it live.

[bebbo]

Originally Posted by wawa

@bebbo
im trying to get scalos compile with your gcc, but a type is missing from stdlib header, as it seems:

/home/wawa/opt/amiga/m68k-amigaos/sys-include/stdlib.h:108:64: error: unknown type name '_mbstate_t'
__stdargs int _mblen_r (struct _reent *, const char* , size_t, _mbstate_t *);

_mbstate_t was a pita (and maybe is) but for some time there were no more problems with it.


Please provide a proper example - mini source plus Makefile or provide at least your command line options.