From owner-freebsd-current Sat Mar 28 16:58:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA05290 for freebsd-current-outgoing; Sat, 28 Mar 1998 16:58:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA05282 for ; Sat, 28 Mar 1998 16:58:23 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id QAA11826; Sat, 28 Mar 1998 16:58:16 -0800 (PST) (envelope-from jdp) Message-Id: <199803290058.QAA11826@austin.polstra.com> To: Greg Lehey cc: current@FreeBSD.ORG Subject: Re: gcc in -current still broken In-reply-to: Your message of "Sun, 29 Mar 1998 09:22:10 +0930." <19980329092210.19096@freebie.lemis.com> Date: Sat, 28 Mar 1998 16:58:15 -0800 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The assembler is too critical of a component to make untested > > commits. If I broke it badly enough, it would be impossible for > > people to recover except by a full reinstall. > > How come? You can keep a copy, or restore it from tape. It's not > like a broken libc. But your libc would have been built with the broken assembler. It and everything else you'd just installed could _all_ be broken. It's admittedly unlikely that the bug would be so subtle that you wouldn't notice it in a make world. On the other hand, it's not going to hurt to wait a few more hours until the thing has been tested a little more. People who are in a rush can use the patch, which I've posted twice to -current. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message