From owner-freebsd-current@FreeBSD.ORG Sun Mar 15 15:28:12 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 3946B1065670; Sun, 15 Mar 2009 15:28:12 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from sarah.protected-networks.net (sarah.protected-networks.net [IPv6:2001:470:1f07:4e1::1]) by mx1.freebsd.org (Postfix) with ESMTP id EC62F8FC12; Sun, 15 Mar 2009 15:28:11 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from toshi.auburn.protected-networks.net (toshi.auburn.protected-networks.net [IPv6:2001:470:1f07:4e1::4]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "Iain Michael Butler", Issuer "Protected Networks Certificate Authority" (verified OK)) (Authenticated sender: imb) by sarah.protected-networks.net (Postfix) with ESMTPSA id C98366284; Sun, 15 Mar 2009 11:28:10 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=protected-networks.net; s=200705; t=1237130891; bh=5FJJKK683HqklCrBnPfbVvwvqlmI8jDHmAgNftnZgyE=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=eKX/FmPbWYiTUyNql3IxhqfWyBAPTKJRQwIKM01okZPkgvuNitMF3W543aX/OI+y6 bRgWq7nVacR7hPrWF87rcnf+91X46ZQeLribY8rjJK5QOiFdzHMK+CC9JM4CdFe DomainKey-Signature: a=rsa-sha1; s=200509; d=protected-networks.net; c=nofws; q=dns; h=message-id:date:from:user-agent:mime-version:to:cc:subject: references:in-reply-to:x-enigmail-version:openpgp:content-type:content-transfer-encoding; b=iCrmdNd0tWU3dINRn71ba5OmacvZKXnNpSN2dTVFJkfkCOizpvpS3QjY5Z20jrSZR OWCNtTFZ1e4Oil616OsJCYTjR9GeCR5tdRNhnTnTl+oPIlxmV/xX79NTbdc0cRn Message-ID: <49BD1E86.9010203@protected-networks.net> Date: Sun, 15 Mar 2009 11:28:06 -0400 From: Michael Butler User-Agent: Thunderbird 2.0.0.19 (X11/20090217) MIME-Version: 1.0 To: Roman Divacky References: <49BD0826.207@protected-networks.net> <20090315151326.GA97191@freebsd.org> In-Reply-To: <20090315151326.GA97191@freebsd.org> X-Enigmail-Version: 0.95.7 OpenPGP: id=0442D492 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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:28:12 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Roman Divacky wrote: > On Sun, Mar 15, 2009 at 09:52:38AM -0400, Michael Butler wrote: >> 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 :) In part, yes. > what was your question again? The 'no-strict-aliasing' parameter was added for a reason (which I can no longer recall :-() so I was curious if I should be looking for related regressions now that it has been removed. That is: 1) if the breakage that prompted its addition has since been resolved to now permit its absence? .. or .. 2) if the c99/gnu99 mode incorporates a re-interpretation (by gcc) of aliasing methods so this parameter is no longer required? Michael -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkm9HoUACgkQQv9rrgRC1JKvmwCfTJ9tplb7gHDXaztQCv/cCC/N Ce4AoJZ9bZStE9TaYsp8a2b31xfRPZHy =8dhG -----END PGP SIGNATURE-----