From owner-freebsd-current Fri Apr 19 17:04:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA12351 for current-outgoing; Fri, 19 Apr 1996 17:04:01 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id RAA12324 for ; Fri, 19 Apr 1996 17:03:59 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id RAA02995; Fri, 19 Apr 1996 17:02:59 -0700 (PDT) cc: Nate Williams , Terry Lambert , kuku@gilberto.physik.rwth-aachen.de (Christoph P. Kukulies), freebsd-current@freefall.freebsd.org Subject: Re: gzipped executables In-reply-to: Your message of "Fri, 19 Apr 1996 16:30:16 PDT." <2744.829956616@time.cdrom.com> Date: Fri, 19 Apr 1996 17:02:59 -0700 Message-ID: <2993.829958579@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > If this is the case, why did it used to work on Pentium processors? > > It also ignores the fact that it also fails on my 486/DX2.. :-) Sorry, just to clarify what I meant here since I can see how Terry would read the above and say "say what?! I was saying that it only failed on *Pentium* processors due to their differing cache architecture! I never said *anything* about the 486!" I expressed my point poorly. What I *meant* to say was that it used to work on all the Intel processor types then began failing on all of them at the same time, from the 486 to the Pentium. This doesn't lead me to believe that the failure is related to any particular processor or cache architecture so much as it is a simple bug which has crept in and whacked the gzip emulator. Jordan