Date: Fri, 28 Sep 2001 14:21:37 -0400 (EDT) From: Andrew Gallatin <gallatin@cs.duke.edu> To: "Matthew Rezny" <mrezny@umr.edu> Cc: "alpha@freebsd.org" <alpha@FreeBSD.ORG> Subject: Re: the -O2 flag Message-ID: <15284.49073.622905.144457@grasshopper.cs.duke.edu> In-Reply-To: <20010928180928.406C137B40C@hub.freebsd.org> References: <20010928180928.406C137B40C@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Matthew Rezny writes: > Now that I"ve created make.conf to set my architecture so that gcc > doesn't crash while compiling KDE with -O as is the default, I have > another question. Somehow it still ends up with -O2 in the Makefiles > that the configure script builds. g++ gives a big warning about known > optimizer bugs on this platform with that switch. Now does this mean > gcc might crash while compiling or that it may produce bad object code? > I've always tried to edit that flag out of makefiles, but this damn > thing has a makefile in every subdirectory so I'd have to edit several > dozen. > Possible bad code -- but with using the -mev56 flag, it may produce OK code. When I built kde, I seem to remember running find with a perl -pi to edit each make file (or configure file). Its been a while.. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15284.49073.622905.144457>