From owner-freebsd-current@FreeBSD.ORG  Wed Feb 11 19:54:34 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 94FF616A4CE
	for <current@FreeBSD.ORG>; Wed, 11 Feb 2004 19:54:34 -0800 (PST)
Received: from VARK.homeunix.com (adsl-68-122-2-18.dsl.pltn13.pacbell.net
	[68.122.2.18])	by mx1.FreeBSD.org (Postfix) with ESMTP id 7222843D31
	for <current@FreeBSD.ORG>; Wed, 11 Feb 2004 19:54:34 -0800 (PST)
	(envelope-from das@FreeBSD.ORG)
Received: from VARK.homeunix.com (localhost [127.0.0.1])
	by VARK.homeunix.com (8.12.10/8.12.10) with ESMTP id i1C3sKOa029800;
	Wed, 11 Feb 2004 19:54:20 -0800 (PST)
	(envelope-from das@FreeBSD.ORG)
Received: (from das@localhost)
	by VARK.homeunix.com (8.12.10/8.12.10/Submit) id i1C3sKtG029799;
	Wed, 11 Feb 2004 19:54:20 -0800 (PST)
	(envelope-from das@FreeBSD.ORG)
Date: Wed, 11 Feb 2004 19:54:20 -0800
From: David Schultz <das@FreeBSD.ORG>
To: Kris Kennaway <kris@obsecurity.org>
Message-ID: <20040212035420.GA29761@VARK.homeunix.com>
Mail-Followup-To: Kris Kennaway <kris@obsecurity.org>,
	Ivan Voras <ivoras@fer.hr>, current@FreeBSD.ORG
References: <c11ba4d1.a4d1c11b@etat.lu> <40288358.2050302@hqst.com>
	<402ABB62.1000000@fer.hr> <20040212013026.GA6864@xor.obsecurity.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040212013026.GA6864@xor.obsecurity.org>
cc: current@FreeBSD.ORG
cc: Ivan Voras <ivoras@fer.hr>
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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Feb 2004 03:54:34 -0000

On Wed, Feb 11, 2004, Kris Kennaway wrote:
> On Thu, Feb 12, 2004 at 12:31:46AM +0100, Ivan Voras wrote:
> > Roop Nanuwa wrote:
> > 
> > >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.
> > 
> > This is interesting - I just compiled lib/libpam with -O2 on RELENG_5_1 
> > and it went without a glitch. Maybe you could hunt it down through the 
> > cvs versions?
> 
> I think that's a red herring.  Either the compiler changed to start
> generating this warning or something else did, but it wasn't due to a
> change in the PAM code.

gcc started caring about aliasing around version 3.0.  Initially,
if you used -fstrict-aliasing on code that had aliasing problems,
there was a chance that it would silently generate bad code.  More
recently, gcc has learned how to detect a number of aliasing
problems and warn about them.  It is true that world no longer
builds with -O2 on i386 *unless* you define NO_WERROR or set WARNS
low enough.