From owner-freebsd-hackers Thu Jul 19 11:41:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id DF20137B401; Thu, 19 Jul 2001 11:41:28 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from wonky.feral.com (mjacob@wonky.feral.com [192.67.166.7]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f6JIfRS66833; Thu, 19 Jul 2001 11:41:28 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Thu, 19 Jul 2001 11:41:20 -0700 (PDT) From: Matthew Jacob Reply-To: To: John Baldwin Cc: Terry Lambert , , Subject: Re: x86 unaligned access followup. In-Reply-To: Message-ID: <20010719113955.H50024-100000@wonky.feral.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > It is very rare that the alpha port is broken as you describe. Sometimes > a bug will have a different affect on the alpha than on x86, but except > for bugs in sys/alpha that x86'ers won't be committing, very few of the bugs > break just the alpha and not the x86 as well. Generally this is true. Most of the alpha vs. x86 issues are found in compilation. Actually, to be fair, we'd have to consider all the kernel subsystems that have *not* in fact been tested on alpha. The dozens of warnings from NetGraph or CODA code indicate that there might be problems there, for instance. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message