Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S266296AbRGBATa>; Sun, 1 Jul 2001 20:19:30 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S266295AbRGBATV>; Sun, 1 Jul 2001 20:19:21 -0400
Received: from imladris.infradead.org ([194.205.184.45]:24082 "EHLO
	infradead.org") by vger.kernel.org with ESMTP id <S266296AbRGBATE>;
	Sun, 1 Jul 2001 20:19:04 -0400
Date: Mon, 2 Jul 2001 01:18:56 +0100 (BST)
From: Riley Williams <rhw@MemAlpha.CX>
X-X-Sender: <rhw@infradead.org>
To: "H. Peter Anvin" <hpa@zytor.com>
cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Re: gcc: internal compiler error: program cc1 got fatal signal
 11]
In-Reply-To: <3B3FB9E1.9090404@zytor.com>
Message-ID: <Pine.LNX.4.33.0107020117210.18977-100000@infradead.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org

Hi Peter.

 >> Wasn't 2.2.12 the kernel that included the `lock halt` bug patch?

 > Perhaps, but is has absolutely nothing to do with the rest of
 > this discussion.

The `lock halt` bug patch was specific to the Cyrix processors (not to
be confused with the `lock registers` patch for the Intel processors,
and I noted that the processor in question was a Cyrix one, hence the
comment.

Best wishes from Riley.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/