From owner-freebsd-current@FreeBSD.ORG Sun Jun 12 02:49:39 2005 Return-Path: X-Original-To: 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 B56EB16A41C; Sun, 12 Jun 2005 02:49:39 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.232]) by mx1.FreeBSD.org (Postfix) with ESMTP id C715743D48; Sun, 12 Jun 2005 02:49:36 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 85FC45123D; Sat, 11 Jun 2005 22:49:23 -0400 (EDT) Date: Sat, 11 Jun 2005 22:49:22 -0400 From: Kris Kennaway To: obrien@freebsd.org, Ruslan Ermilov , Dag-Erling Sm?rgrav , freebsd-current@freebsd.org Message-ID: <20050612024922.GA57913@xor.obsecurity.org> References: <20050609234619.AD1F67306E@freebsd-current.sentex.ca> <84dead720506091950779d1661@mail.gmail.com> <86oeae3d8f.fsf@xps.des.no> <20050610071828.GB78035@ip.net.ua> <867jh23bwh.fsf@xps.des.no> <20050610074706.GE78035@ip.net.ua> <20050612022105.GB67746@dragon.NUXI.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="lrZ03NoBR/3+SXJZ" Content-Disposition: inline In-Reply-To: <20050612022105.GB67746@dragon.NUXI.org> User-Agent: Mutt/1.4.2.1i Cc: Subject: Re: [current tinderbox] failure on ...all... 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, 12 Jun 2005 02:49:39 -0000 --lrZ03NoBR/3+SXJZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jun 11, 2005 at 07:21:05PM -0700, David O'Brien wrote: > On Fri, Jun 10, 2005 at 10:47:06AM +0300, Ruslan Ermilov wrote: > > On Fri, Jun 10, 2005 at 09:32:14AM +0200, Dag-Erling Sm?rgrav wrote: > > > Ruslan Ermilov writes: > > > > And if you feel that -fno-strict-aliasing is evil, why not dike it > > > > out from sys.mk? > > >=20 > > > 'ncvs annotate /usr/src/share/mk/sys/mk | grep aliasing' and you'll > > > realize that any attempt to touch it would result in a huge flamewar. > > >=20 > > I don't see a flamewar, only the mention that it breaks some notable > > ports. If it's not suitable for ports, then we should invent a mean > > to compile only src/ *without* -fno-strict-aliasing. >=20 > I tried. But Kris refused to consider the following for committing. > The problem is something like 3 ports will not build with > "-fno-strict-aliasing". Those are the gcc28, gnat[*] ports. No, I was waiting for you to provide the patch that has zero net damage, i.e. which fixes those 3 ports and leaves nothing broken for someone else to clean up. Kris --lrZ03NoBR/3+SXJZ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFCq6KyWry0BWjoQKURAn5BAKD3qD4ZEKtsgAO6d2nvj7qHHhAWbACg0d16 7+1YRU5bHM3n2a+yUVsUX5c= =mtyC -----END PGP SIGNATURE----- --lrZ03NoBR/3+SXJZ--