Re: m68k does not imply m68020-60

Andrew Cagney <[email protected]> Thu, 26 Nov 2015 13:24:44 -0500
Newsgroups gmane.comp.mozilla.devel.nspr
Message-ID <CAJeAr6uTwgg2dtOHwyDUCaPv=1CG_ZJQ-mZuRxLPLDBgk0XA+A@mail.gmail.com>
On 26 November 2015 at 11:39, Wan-Teh Chang <[email protected]> wrote:
> On Thu, Nov 26, 2015 at 6:55 AM, Andrew Cagney <[email protected]> wrote:
>> Having the compiler generate m68020-60 instructions made running on my
>> coldfire very difficult :-(  I think it is better to just honour the
>> compiler.
>
> Hi Andrew,
>
> Thank you for the post. I did a search for "m68k" in the NSPR source
> tree. I believe you are referring to this m68k case in the
> configure.in script:
>
> 1859     m68k)
> 1860         CFLAGS="$CFLAGS -m68020-60"
> 1861         CXXFLAGS="$CXXFLAGS -m68020-60"
> 1862         ;;
>
> The revision history shows this was added in 1999 and 2002:
>
> https://hg.mozilla.org/projects/nspr/rev/29227fdc9a15
> https://hg.mozilla.org/projects/nspr/rev/879b717836d9
>
> I think we should just delete the m68k case from the configure.in
> script. Agreed?

Yes.  I thought I'd attached the below which does just that:

--- nspr-4.10.9/nspr/configure.in.orig    2015-11-25 15:17:14.732725317 -0500
+++ nspr-4.10.9/nspr/configure.in    2015-11-25 20:09:38.299725384 -0500
@@ -1857,8 +1865,4 @@
         fi
         ;;
-    m68k)
-        CFLAGS="$CFLAGS -m68020-60"
-        CXXFLAGS="$CXXFLAGS -m68020-60"
-        ;;
     esac
     ;;

thanks.
Andrew

> Wan-Teh