From owner-freebsd-current@FreeBSD.ORG Sun Mar 15 15:13:58 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 237331065676 for ; Sun, 15 Mar 2009 15:13:58 +0000 (UTC) (envelope-from rdivacky@vlk.vlakno.cz) Received: from vlakno.cz (77-93-215-190.static.masterinter.net [77.93.215.190]) by mx1.freebsd.org (Postfix) with ESMTP id 4051C8FC20 for ; Sun, 15 Mar 2009 15:13:55 +0000 (UTC) (envelope-from rdivacky@vlk.vlakno.cz) Received: from localhost (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id 6597D9CB04D; Sun, 15 Mar 2009 16:13:38 +0100 (CET) X-Virus-Scanned: amavisd-new at vlakno.cz Received: from vlakno.cz ([127.0.0.1]) by localhost (lev.vlakno.cz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vbPkOydPLlwf; Sun, 15 Mar 2009 16:13:27 +0100 (CET) Received: from vlk.vlakno.cz (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id E79029CB121; Sun, 15 Mar 2009 16:13:26 +0100 (CET) Received: (from rdivacky@localhost) by vlk.vlakno.cz (8.14.3/8.14.3/Submit) id n2FFDQGm097655; Sun, 15 Mar 2009 16:13:26 +0100 (CET) (envelope-from rdivacky) Date: Sun, 15 Mar 2009 16:13:26 +0100 From: Roman Divacky To: Michael Butler Message-ID: <20090315151326.GA97191@freebsd.org> References: <49BD0826.207@protected-networks.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49BD0826.207@protected-networks.net> User-Agent: Mutt/1.4.2.3i Cc: freebsd-current Subject: Re: no-strict-aliasing? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Sun, 15 Mar 2009 15:13:58 -0000 On Sun, Mar 15, 2009 at 09:52:38AM -0400, Michael Butler wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I note that, with the alteration of compile parameters for the kernel, > the option "-fno-strict-aliasing" is no longer used (for i386). indeed.. it seems that -fno-strict-aliasing is used only when building modules and/or building on amd64. I dont understand why > Does the shift to c99/gnu99 mode change the behaviour of the compiler > such that this is unnecessary or should I be "on the lookout" for > obscure failures? ;-) are you referring to my recent commit? that affected world only. kernel has been building with c99 for.. a long time :) what was your question again? roman