Re: [m68k] Fix option handling for -m68020-40 and -m68020-60

2012-10-28 Thread Gunther Nikl
Andreas Schwab wrote: Gunther Nikl gn...@users.sourceforge.net writes: The patch should be installed on trunk and on the 4.7 branch. Thanks, done. The 4.7 branch required some adjustment, since it's not compiled as C++. Right. Maybe a better solution would have been then to only change

Re: [m68k] Fix option handling for -m68020-40 and -m68020-60

2012-10-26 Thread Andreas Schwab
Gunther Nikl gn...@users.sourceforge.net writes: The patch should be installed on trunk and on the 4.7 branch. Thanks, done. The 4.7 branch required some adjustment, since it's not compiled as C++. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B

Re: [m68k] Fix option handling for -m68020-40 and -m68020-60

2012-10-25 Thread Gunther Nikl
Andreas Schwab wrote: Gunther Nikl gn...@users.sourceforge.net writes: While working with GCC 4.7, I noticed that the -m68020-40 and -m68020-60 options are broken. Broken in which way? These compound options are supposed to cause m68k.c/m68k_option_override to set m68k_cpu_entry and

[m68k] Fix option handling for -m68020-40 and -m68020-60

2012-10-23 Thread Gunther Nikl
Hello, While working with GCC 4.7, I noticed that the -m68020-40 and -m68020-60 options are broken. This bug was introduced in May 2011 with the patch at http://gcc.gnu.org/ml/gcc-patches/2011-04/msg02278.html. The code in m68k_option_override to set cpu and tune doesn't trigger when using

Re: [m68k] Fix option handling for -m68020-40 and -m68020-60

2012-10-23 Thread Andreas Schwab
Gunther Nikl gn...@users.sourceforge.net writes: While working with GCC 4.7, I noticed that the -m68020-40 and -m68020-60 options are broken. Broken in which way? Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 And