GCC 6.2 toolchain for AmigaOS 3

[fstltna]

Originally Posted by bebbo

which version did you pick?

I haven't, still not working...

[emufan]

I may have found a solution to prevent the freeze feature when using 'make -jN' under cygwin.
same with building gcc6 using "--threads N".

export SHELL=CMD

I put that into my ~/.bashrc - otherwise I would forget about that sooner or later.
for now it does work.

#1) btw. I build SDL_image with gcc6 "-noixemul -m68020-40 -msoft-float -g -O2"
this does crash the gcc3 linker --> when building without "-O2" - the lib does link without problem.

[Marlon_]

Originally Posted by emufan

I may have found a solution to prevent the freeze feature when using 'make -jN' under cygwin.
same with building gcc6 using "--threads N".

export SHELL=CMD

I put that into my ~/.bashrc - otherwise I would forget about that sooner or later.
for now it does work.

#1) btw. I build SDL_image with gcc6 "-noixemul -m68020-40 -msoft-float -g -O2"
this does crash the gcc3 linker --> when building without "-O2" - the lib does link without problem.

When you're compiling libSDL-1.2.15 from github, which Makefile are you using? Because Makefile.bax is the only one enabling the Vampire exclusive instructions.

[emufan]

Originally Posted by Marlon_

When you're compiling libSDL-1.2.15 from github, which Makefile are you using? Because Makefile.bax is the only one enabling the Vampire exclusive instructions.

I was using the default Makefile and did some editing, until it fit, see the attached one.

[Marlon_]

Originally Posted by emufan

I was using the default Makefile and did some editing, until it fit, see the attached one.

Ah, well, then none of your ports are actually getting any AMMX benefits on Vampire systems. Just fyi. Use the bax makefile like the readme says on the github page in order to get Vamp support.

[emufan]

Originally Posted by Marlon_

Ah, well, then none of your ports are actually getting any AMMX benefits on Vampire systems. Just fyi. Use the bax makefile like the readme says on the github page in order to get Vamp support.

ok, thnx for info. I'll build a *.bax one now.
does it retain compatibility to non-AMMX machines?

video/amigaos/SDL_cgxvideo.c:34:23: error: expected identifier or
‘(’ before numeric constant
 #define Apollo_AMMXon 0
                       ^
./video/apollo/apolloammxenable.h:24:22: note: in expansion of macro ‘Apollo_AMMXon’
 extern unsigned char Apollo_AMMXon;
                      ^~~~~~~~~~~~~


video/amigaos/SDL_cgxvideo.c:
34: #define Apollo_AMMXon 0
35:
36: #include "SDL_config.h"

any idea?

[Marlon_]

Yes, the AMMX asm-files checks which CPU it is and uses the appropriate instructions depending on CPU. Makefile.bax uses VASM to compile these files before including them in the gcc6 linker.

[emufan]

Originally Posted by Marlon_

Yes, the AMMX asm-files checks which CPU it is and uses the appropriate instructions depending on CPU. Makefile.bax uses VASM to compile these files before including them in the gcc6 linker.

ok, good news. any idea about the error I added above? using gcc6.

[Marlon_]

Originally Posted by emufan

ok, good news. any idea about the error I added above? using gcc6.

Hmm, no clue. I had to modify the makefile a bit and some sources to get it to compile on the gcc6 toolchain myself. Make sure the prefixes are correct and such.

[emufan]

somehoiw I made a makefile mix with the non-AMMX version, it did build a lib,
which has some apollo functions included. differs in size.
I'll let xboxnow test the one (edgar)

[bebbo]

Merry Christmas!

I just switched the binutils to amiga hunk format to enable the now supported memory qualifiers

__chip int yeah_in_chip = 1234;
__fast int oh_so_fast = 999;
__far int no_base_rel = 456; // never use baserel (a4) addressing

.bss* is selected if there is no intializer, .data* if there is some.

The examples do work and way more.

Happy New Year :-)

[Samurai_Crow]

Sweet!

[alpine9000]

Nice work bebbo!

[emufan]

Originally Posted by bebbo

I just switched the binutils to amiga hunk format to enable the now supported memory qualifiers

do we now have amiga-hunk-format object files - like seen with StormC4?

[bebbo]

Originally Posted by emufan

do we now have amiga-hunk-format object files - like seen with StormC4?

Yes.

• The new version of m68k-amigaos-as creates object (.o) files in amiga-hunk-format.
• The new version of m68-amigaos-ar creates libs (.a) files in amiga-hunk-format
• The linker m68k-amigaos-ld is still creating programs in amiga-hunk-format plus it can still handle objects and libraries in aout format.
• The aout specific constructors via .stab/.stabstr are supported in amiga-hunk-format: the content is passed in debug sections and processed by the linker.

[bebbo]

Here a simple test program which creates all kind of memory hunks:

mem.c:

#include <stdio.h>

int dat[] = {1, 2, 3, 4};
__chip int cdat[] = {11, 12, 13, 14};
__far int fdat[] = {121, 122, 123, 124};
__fast int adat[] = {221, 222, 223, 224};

__chip int ucdat[4];
__far int ufdat[4];
__fast int uadat[4];

int iii;

int foo(int i) {
  return iii += i;
}

int main(int argc, char ** argv) {
  printf("%08x %08x %08x %08x\n", dat, cdat, fdat, adat);
  foo(dat[2] + cdat[2] + fdat[2] + adat[2]);

  adat[2] = ucdat[3] = cdat[3];
  fdat[2] = uadat[3] = adat[3];
  cdat[2] = ufdat[3] = fdat[3];

  return dat[1] + cdat[1] + fdat[1] + adat[1] + iii;
}

compile it with

m68k-amigaos-gcc -noixemul -Os -fbaserel mem.c -o mem -s

and you get these hunks:

hunk 000003f3,      HUNK_HEADER,          0
8 sections, 0 - 7
sizes: 6400, 964, 16(c), 16(f), 16, 16(c), 16(f), 16
hunk 000003e9,        HUNK_CODE,       6400
hunk 000003ec,     HUNK_RELOC32,        376
hunk 000003ea,        HUNK_DATA,        796
hunk 000003ec,     HUNK_RELOC32,         68
hunk 000003ea,        HUNK_DATA,         16
hunk 000003ea,        HUNK_DATA,         16
hunk 000003ea,        HUNK_DATA,         16
hunk 000003eb,         HUNK_BSS,         16
hunk 000003eb,         HUNK_BSS,         16
hunk 000003eb,         HUNK_BSS,         16

[alkis]

Man, that's sweet! Thanks for your effort.

[arti]

Any chance we get gprof?

[emufan]

Originally Posted by bebbo

Yes.

cool, thanks

[pipper]

Next on my wishlist would be a gdbserver / gdbclient that can allow for remote, source level debugging. I would love to fully use qtcreator on a Linux or Windows box to do cross platform development :-D