Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 01 Oct 2001 07:52:12 +0200
From:      "Idar Tollefsen" <Idar.Tollefsen@baerum.kommune.no>
To:        <alpha@freebsd.org>
Cc:        <mrezny@umr.edu>
Subject:   Re: the -O2 flag
Message-ID:  <sbb820c0.002@mail.baerum.kommune.no>

next in thread | raw e-mail | index | archive | help
> > 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..

Another thing to note is that it adds the flags from make.conf _after_
the KDE makefile flags. The result is that the -O? you specified in
make.conf is the one that comes last, and according to the gcc
man pages, the -O parameter specified last is the one that is used.

I suspect that it spews out those warnings simply because -O2 is
part of the command line at all, without necessarily beeing the one
that is used.



- IT



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?sbb820c0.002>