From owner-freebsd-stable Sun Jul 28 21:47:14 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D170C37B400 for ; Sun, 28 Jul 2002 21:47:12 -0700 (PDT) Received: from ns.itga.com.au (ns.itga.com.au [202.53.40.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6945A43E65 for ; Sun, 28 Jul 2002 21:47:11 -0700 (PDT) (envelope-from gnb@itga.com.au) Received: from lightning.itga.com.au (lightning.itga.com.au [192.168.71.20]) by ns.itga.com.au (8.9.3/8.9.3) with ESMTP id OAA76108; Mon, 29 Jul 2002 14:47:09 +1000 (EST) (envelope-from gnb@itga.com.au) Received: from lightning.itga.com.au (localhost [127.0.0.1]) by lightning.itga.com.au (8.9.3/8.9.3) with ESMTP id OAA22147; Mon, 29 Jul 2002 14:47:09 +1000 (EST) Message-Id: <200207290447.OAA22147@lightning.itga.com.au> X-Mailer: exmh version 2.4 05/15/2001 with nmh-1.0.4 From: Gregory Bond To: Clifton Royston Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Is use of -O2 still deprecated for buildworld in -stable? In-reply-to: Your message of Sat, 27 Jul 2002 19:19:45 -1000. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 29 Jul 2002 14:47:09 +1000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > My understanding is that whether or not -O2 *should* produce exactly > equivalent code to -O, there are recurrent reports of people having > trouble doing a buildworld with -O2 in -stable or in 4.x release > trains, where their problems go away when they revert back to -O. The TCP checksum code seems to be the most common culprit - compiling with -O2 seems to create checksum routines that fail in certain corner cases, meaning some hosts or some data patterns cause TCP sessions to freeze. [I've not seen it myself, but it has been reported here a couple of times.] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message