Re: Convert legacy m68k options to .opt aliases

On Thu, 14 Apr 2011, Gunther Nikl wrote: > 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? Whatever options you want to match that spec shoul

Re: Convert legacy m68k options to .opt aliases

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 no

Re: Convert legacy m68k options to .opt aliases

On Tue, 12 Apr 2011, Gunther Nikl wrote: > I was under the impression that the used (bin-)utils had to offer > required target support (instructions, directives, object file format) > to be usable with GCC. AFAICT newer binutils versions (in my case And command-line options. > >2.9.1) configured

Re: Convert legacy m68k options to .opt aliases

Joseph S. Myers wrote: > On Thu, 7 Apr 2011, Gunther Nikl wrote: > >>> an alias for -mcpu=68332 rather than -mcpu=cpu32, to match the old >>> code in m68k_handle_option.) This significantly simplifies the >>> multilibs code in t-mlibs, since it no longer needs to handle those >>> old-style option

Re: Convert legacy m68k options to .opt aliases

On Thu, 7 Apr 2011, Gunther Nikl wrote: > > an alias for -mcpu=68332 rather than -mcpu=cpu32, to match the old > > code in m68k_handle_option.) This significantly simplifies the > > multilibs code in t-mlibs, since it no longer needs to handle those > > old-style options (and all cases where two

Re: Convert legacy m68k options to .opt aliases

On Wed, Apr 06, 2011 at 10:04:37PM +, Joseph S. Myers wrote: > Similar to , > this patch converts legacy m68k options for non-ColdFire CPUs into > aliases for the corresponding -mcpu= options. (Note that -mcpu32 is While I agree with th