linux-mips-fnet
[Top] [All Lists]

Re: -fno-strict-aliasing problem in the latest 2.3

To: Harald Koerfgen <Harald.Koerfgen@home.ivm.de>
Subject: Re: -fno-strict-aliasing problem in the latest 2.3
From: Ralf Baechle <ralf@oss.sgi.com>
Date: Thu, 17 Feb 2000 14:25:29 +0100
Cc: "Gleb O. Raiko" <raiko@niisi.msk.ru>, linux-mips@fnet.fr, SGI Linux <linux@cthulhu.engr.sgi.com>
In-reply-to: <XFMail.000216190319.Harald.Koerfgen@home.ivm.de>
References: <38A91E19.CE7A9890@niisi.msk.ru> <XFMail.000216190319.Harald.Koerfgen@home.ivm.de>
On Wed, Feb 16, 2000 at 07:03:19PM +0100, Harald Koerfgen wrote:

> On 15-Feb-00 Gleb O. Raiko wrote:
> > There is a problem with the way main Makefile determines whether the
> > compiler suports -fno-strict-aliasing. Namely, Makefile blindly gets $CC
> > and tries to feed this option to it. Unfortunately, we set CC to proper
> > mips[el]-linux-gcc later in arch/mips/Makefile, so the main Makefile
> > just checks against native gcc. On RH6.1 with latest cross tool rpms
> > installed, I get cc1: Invalid option `-fno-strict-aliasing' during
> > comppilation, obviously.
> 
> I am not exactly shure if it has ill side effects or if this may not be wanted
> for some reason, but the attached patch fixes that for me.
> 
> OK to commit?

Yes, my solution is identical, so who commits first commits first :)

  Ralf

<Prev in Thread] Current Thread [Next in Thread>