From owner-freebsd-hackers Sat Jun 7 02:16:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA07688 for hackers-outgoing; Sat, 7 Jun 1997 02:16:05 -0700 (PDT) Received: from shadows.aeon.net (bsdhack@shadows.aeon.net [194.100.41.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA07681 for ; Sat, 7 Jun 1997 02:16:01 -0700 (PDT) Received: (from bsdhack@localhost) by shadows.aeon.net (8.8.5/8.8.3) id MAA04799; Sat, 7 Jun 1997 12:15:20 +0300 (EET DST) From: mika ruohotie Message-Id: <199706070915.MAA04799@shadows.aeon.net> Subject: Re: gcc -m486, gcc -O2 In-Reply-To: from Craig Johnston at "Jun 6, 97 03:52:17 pm" To: craig@gnofn.org (Craig Johnston) Date: Sat, 7 Jun 1997 12:15:20 +0300 (EET DST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Is there any reason -O2 would not be a good idea for kernel/make > world in make.conf? I notice that the suggested use is -O2 for > everything else and -O for the kernel. i've gotten -O2 on both from like the dawn of the days... meaning that ever since i installed this machine as 2.0-CURRENT back in 94, i put that '-O2 -m486 -pipe' into the COPTFLAGS line in /etc/make.conf and i doubt i've gotten myself bitten in the leg coz of it, and i do upgrade my machine into latest -CURRENT like weekly... ofcourse, occasionally, like now, my kernel acts bit weird in certain conditions, but i really doubt it's that -O2 causing those... i remember someone mentioning some time ago that -O3 caused weirdoes, but then again, other people said it's ok... (and if anyone has other flags to suggest for world/kernel, i'm always ready to test, even though this is my home "production" server) > Craig mickey