From owner-freebsd-current Sun Sep 15 0:23:33 2002 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 ECA4537B400 for ; Sun, 15 Sep 2002 00:23:31 -0700 (PDT) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 002C443E65 for ; Sun, 15 Sep 2002 00:23:30 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id RAA03303; Sun, 15 Sep 2002 17:23:25 +1000 Date: Sun, 15 Sep 2002 17:31:42 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Julian Elischer Cc: FreeBSD current users Subject: Re: Very important bug.. In-Reply-To: Message-ID: <20020915171435.I1742-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 14 Sep 2002, Julian Elischer wrote: > Well to all 2 of you that would ever considering running > FreeBSD 1.1 binaries on -current anyhow... > > Everything goes along great until you hit a pid > 32768 > then everything stops > > apparently the code in libc in FreeBSD1.1 assumes that pids are < 32k > and CHECKS it.. :-) [It was a sign extension bug. There are also some sign exension bugs at the 2^32 boundary. E.g., olseek() silently truncates large offsets mod 2^32.] > My aim was to time a "make world" in a 1.1 jail under -current with > a modern machine. (just to see how much slower we've made everything) > > so Everything was screaming past at a very fast rate until: I guess it would be about twice as slow. Others made gcc a little more than twice as slow and we can only add a little to that, especially with only userland differences. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message