From: "H. Peter Anvin" <hpa@zytor.com>
To: Riley Williams <rhw@MemAlpha.CX>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Re: gcc: internal compiler error: program cc1 got fatal signal 11]
Date: Sun, 01 Jul 2001 17:21:32 -0700 [thread overview]
Message-ID: <3B3FBE8C.80803@zytor.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0107020117210.18977-100000@infradead.org>
Riley Williams wrote:
> 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.
>
Oh. Sorry, I don't know about "lock halt" and its effects. However, if
it refers to the instruction sequence LOCK HLT I find it hard to believe
it would have the symptoms described.
-hpa
next prev parent reply other threads:[~2001-07-02 0:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-29 12:48 [Re: gcc: internal compiler error: program cc1 got fatal signal 11] Jesse Pollard
2001-06-29 14:20 ` szonyi calin
2001-06-29 18:53 ` Albert D. Cahalan
2001-07-01 23:25 ` H. Peter Anvin
2001-07-02 0:00 ` Riley Williams
2001-07-02 0:01 ` H. Peter Anvin
2001-07-02 0:18 ` Riley Williams
2001-07-02 0:21 ` H. Peter Anvin [this message]
2001-07-02 0:27 ` Riley Williams
2001-06-29 15:39 ` gcc: internal compiler error: program cc1 got fatal signal 11 David Relson
-- strict thread matches above, loose matches on Subject: below --
2001-07-03 5:51 [Re: gcc: internal compiler error: program cc1 got fatal signal 11] Tha Phlash
2001-06-29 16:28 Jesse Pollard
2001-06-29 5:23 Blesson Paul
2001-06-29 7:29 ` Erik Mouw
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3B3FBE8C.80803@zytor.com \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rhw@MemAlpha.CX \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox