Date: Wed, 11 Feb 2004 17:30:26 -0800 From: Kris Kennaway <kris@obsecurity.org> To: Ivan Voras <ivoras@fer.hr> Cc: current@freebsd.org Subject: Re: -fno-strict-aliasing Message-ID: <20040212013026.GA6864@xor.obsecurity.org> In-Reply-To: <402ABB62.1000000@fer.hr> References: <c11ba4d1.a4d1c11b@etat.lu> <40288358.2050302@hqst.com> <402ABB62.1000000@fer.hr>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] 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. Kris [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAKtcxWry0BWjoQKURAvGBAKCzocxOoaZFVSf3CfXHvD6Tm0XP6ACgoY8G 2HzYIr+Bn/lfjpLHyVFvFJk= =/nYr -----END PGP SIGNATURE-----home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040212013026.GA6864>