4 messages in org.freebsd.freebsd-alphaRe: the -O2 flag| From | Sent On | Attachments |
|---|---|---|
| Matthew Rezny | Sep 28, 2001 11:09 am | |
| Andrew Gallatin | Sep 28, 2001 11:21 am | |
| David O'Brien | Sep 28, 2001 7:16 pm | |
| Idar Tollefsen | Sep 30, 2001 10:51 pm |
| Subject: | Re: the -O2 flag | |
|---|---|---|
| From: | Idar Tollefsen (Idar...@baerum.kommune.no) | |
| Date: | Sep 30, 2001 10:51:50 pm | |
| List: | org.freebsd.freebsd-alpha | |
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 majo...@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message