From owner-freebsd-current@FreeBSD.ORG Mon Feb 9 23:08:06 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A0E9016A4CE for ; Mon, 9 Feb 2004 23:08:06 -0800 (PST) Received: from mout.perfora.net (mout.perfora.net [217.160.230.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8BFFC43D1D for ; Mon, 9 Feb 2004 23:08:06 -0800 (PST) (envelope-from roop@hqst.com) Received: from [217.160.230.51] (helo=smtp.perfora.net) by mout.perfora.net with esmtp (Exim 3.35 #1) id 1AqS03-0000u5-00; Tue, 10 Feb 2004 02:08:03 -0500 Received: from [24.82.165.92] (helo=hqst.com) by smtp.perfora.net with asmtp (Exim 3.35 #1) id 1AqS02-000622-00; Tue, 10 Feb 2004 02:08:02 -0500 Message-ID: <40288358.2050302@hqst.com> Date: Mon, 09 Feb 2004 23:08:08 -0800 From: Roop Nanuwa User-Agent: Mozilla Thunderbird 0.5+ (Windows/20040207) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kris Kennaway References: <20040209022820.00faa408@pyro.convolution.ti> <20040209043217.GA1009@xor.obsecurity.org> <4027871E.8080800@mindspring.com> <20040209215345.GA21980@xor.obsecurity.org> In-Reply-To: <20040209215345.GA21980@xor.obsecurity.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: "Bruno T." cc: Richard Coleman cc: freebsd-current@freebsd.org Subject: Re: -fno-strict-aliasing X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Feb 2004 07:08:06 -0000 Kris Kennaway wrote: >On Mon, Feb 09, 2004 at 08:11:58AM -0500, Richard Coleman wrote: > > >>Kris Kennaway wrote: >> >> >> >>>On Mon, Feb 09, 2004 at 02:28:20AM -0200, Bruno T. wrote: >>> >>> >>> >>>>Hi everyone. >>>>i'm pretty new to bsd, but i have some background in linux development >>>>and for what i have seen until now, i must say that -CURRENT is rather >>>>impressive, congrats ! >>>> >>>>I was rebuilding my base sys and noticed that any compiler flag >>>>that implies -fstrict-aliasing (like -O2) would break some few things, >>>>adding "-fno-strict-aliasing" to "CFLAGS+=" in these makefiles >>>>solves the problem for now. >>>> >>>> >>>Don't do that then :-) >>> >>>Kris >>> >>> >>Although it's not urgent, I don't see why the aliasing problems can't be >>fixed. I think it would be more honest if the party line was "FreeBSD >>has bugs, so we can't use -O2 right now" rather than the standard reply >>of "-O2 is not supported, don't even try". >> >> > >It's "don't even try unless you plan to fix them". > >Kris > > I did a buildworld earlier today with -O2 on and had to modify about 4 makefiles to get it to compile. That's not too bad. I already submitted a patch to fix one (libexec/ypxfr) of them. Working on a second one (libc/isinf) now. Both of these are relatively trivial. On the other hand, one of the last two left is in libpam and I don't think I can even begin to fix that, though. Hopefully someone more familiar with it will be able to take a crack at it sooner or later. --roop