From owner-freebsd-stable Wed Mar 7 2:55:45 2001 Delivered-To: freebsd-stable@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-158.dsl.lsan03.pacbell.net [63.207.60.158]) by hub.freebsd.org (Postfix) with ESMTP id 1412837B718 for ; Wed, 7 Mar 2001 02:55:29 -0800 (PST) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 6994566E1B; Wed, 7 Mar 2001 02:55:19 -0800 (PST) Date: Wed, 7 Mar 2001 02:55:19 -0800 From: Kris Kennaway To: Jordan Hubbard Cc: kris@obsecurity.org, ohartman@klima.physik.uni-mainz.de, antony@abacus.co.uk, freebsd-stable@FreeBSD.ORG Subject: Re: ARCH flag in new make.conf Message-ID: <20010307025519.A37634@mollari.cthul.hu> References: <20010307015036.A36721@mollari.cthul.hu> <20010307020500X.jkh@osd.bsdi.com> <20010307024456.A37349@mollari.cthul.hu> <20010307024729G.jkh@osd.bsdi.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="7AUc2qLy4jB3hD7Z" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010307024729G.jkh@osd.bsdi.com>; from jkh@osd.bsdi.com on Wed, Mar 07, 2001 at 02:47:29AM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --7AUc2qLy4jB3hD7Z Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Mar 07, 2001 at 02:47:29AM -0800, Jordan Hubbard wrote: > Well, I can certainly understand that perspective. What would you > say to one of the following compromises: >=20 > a) We make a concerted effort to reproduce Mr Hartman's breakage > and only retain the warning message if we or some reasonable > proxy person manages to do so. Actually he's already doing this -- I'll look forward to hearing the results. Of course, I'm not ruling out the existence of a specific gcc bug which is causing some code to fail -- after all, we all know gcc is far from bug-free -- but I think the fact that a lot of people use -march with no ill effects says that it's at least "mostly safe". We also need to draw the distinction between the various values of -march, since what is broken for one probably won't be broken for the others. > b) We retain the warning but tone it down a lot, simply suggesting > that it *might* hurt you if you used it. I would also welcome any > suggestions on that wording. I'd be happier with a warning which suggests people remove the CPUTYPE setting as a step in the debugging of runtime failures, and remove the text which suggests it's not appropriate to be used by default. Kris --7AUc2qLy4jB3hD7Z Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6phOXWry0BWjoQKURAjv9AJ9YD9teWaOmGQMGl5NIifBhRkmSsgCg3Yag bTZA3x9bY1yuVvp+eafWQ3I= =Wsem -----END PGP SIGNATURE----- --7AUc2qLy4jB3hD7Z-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message