Joseph S. Myers wrote:
>
> m68k-aout was obsoleted in 4.4 and removed in 4.5 - while some OSes
> with various odd object file formats are still supported, various
> newer features such as LTO may not work so well with them.
I am aware that generic m68k-aout as target was deprecated and is gone
now. Apparently that didn't affect my target. I know that eg LTO will
never be available for a.out object files.
>> Is with your change really no way to test/pass the original options
>> to assembler/linker?
>
> You could write specs that check for the -mcpu= options and translate
> them back to old-style options acceptable to your assembler and linker.
Yes, that would work and the assembler part is easier that I expected.
The following is inspired by something I noticed in the alpha port:
%{march=*:-m%*} %{mcpu=*:-m%*}
However, the link spec seems to be harder.
"%{m68020-*|m68040|m68060:-fl libm020}"
Do I have to replace every m680x0 option with a matching mcpu= (maybe
even together with a march=) option?
> You won't be able to use the generic m68k.h ASM_CPU_SPEC, so all the
> complexity of supporting old assemblers falls on your port, but it should
> be possible - you just can't pass through the options without translating
> them.
The port doesn't use the generic ASM_SPECs. AFAIK the port never used
the generic definitions and I kept it that way because I felt more
comfortable using custom definitions.
So problem (almost) solved thanks to the versatile SPEC machinery.
Regards,
Gunther
