GCC 4.5.0 Amigaos 68k Compiler CYGWIN Hostet

[Piru]

the default of the compiler is that FPU return values are always in d0 and d1.the reason is in that way there can work software float.

The linux 68k elf GCC use the FPU for return, i can too switch it easy on(i have get answer in GCC ML what need change), but here must be sure that all libs are fpu version and all libs need recompile.

but when such a big step is do and all libs need make new, then better change AOS GCC that it use elf format.so its more easy to have newest binutils for this.
in elf can also work the LTO.

Well that makes absolutely no sense whatsoever.

Care to explain in simple terms why the binaries would need to be ELF all the sudden?

[bernd_afa]

Well that makes absolutely no sense whatsoever.

Care to explain in simple terms why the binaries would need to be ELF all the sudden?

i think nobody add LTO support for a.out.see your link on docu.

sooner or later the old a.out(which amiga use) format in GCC is drop too.currently i have not build a new binutils for 68k because they have drop the a.out Format in binutils.but luckily the linker and assembler need not change, but its not possible with easy work to build new gprof gdb etc.

see also a.out

http://en.wikipedia.org/wiki/A.out

The a.out Format is move to elf.
So to make things more easy, or need important new gprof or gdb or assembler(for Coldfire instructions) or linker using elf on AOS is better.

but all have time, currently i miss not elf.
change is easy, but only problem is there need build linker libs new.
and when there is no big reason to do that, then no elf is need

[Piru]

i think nobody add LTO support for a.out.
sooner or later the old a.out(which amiga use) format in GCC is drop too.

Yeah fine, but why would it require that the final resulting executables be ELF, too?

[bernd_afa]

Yeah fine, but why would it require that the final resulting executables be ELF, too?

i think a linker does only put code peaces together and when the code that GCC produce is in elf, then the resulting output need too in elf.the disadvantage that all the lib files need in elf is here too.thats also same as when use clib2 or newlib on OS4 or clib2 or ixemul on 68k.

and write a linker that create from the elf output the amiga output is i think lots work.
and the problem is also that there need special ports for gdb and binutil.

with the little work to support elf files in loadseg, you can use all upto data linux 68k-elf gcc/binutil stuff in future and you have no extra work in future.

[bernd_afa]

Yeah fine, but why would it require that the final resulting executables be ELF, too?

as i guess right, mxing of files do not work well.i search for

linker a.out elf mix

and i find this thread

http://blog.gmane.org/gmane.comp.gnu.binutils/month=20080501/page=2

Seem Atari go too the elf way.

but there is also great news see, there are convert tools here in binutil (objcopy), that can convert existing libs into the elf Format.

so there need not old lib recompile, only convert to use on a elf linker.

[billt]

Cool. I've been thinking of looking for a newer gcc version for 68k. I don't know that I need special Amiga tweaks for it, but I do need it for Linux not Cygwin. So I'll try your docs and make one for amd64 ubuntu host. (I run Linux in a virtual machine under Windows instead of Cygwin)

[billt]

The C++ includes and libs can download from other link.

What other link?

[NovaCoder]

did anyone ever get anywhere with this, anyone mange to build a working 68k exe using GCC 4.5.0?

Anyone know if AmiDevCPP is ever going to be udpated to include GCC v4.5.0 support?

And finally is GCC 4.5.0 any good on 68k or should I stick with GCC v3.3 (AmiDevCPP)?

Thanx