From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: mikpe@csd.uu.se (Mikael Pettersson)
Cc: alan@lxorguk.ukuu.org.uk, bernds@redhat.com,
FrankZhu@viatech.com.cn, linux-kernel@vger.kernel.org,
mikpe@csd.uu.se
Subject: Re: PROBLEM:Illegal instruction when mount nfs file systems using
Date: Fri, 29 Jun 2001 00:11:52 +0100 (BST) [thread overview]
Message-ID: <E15Fkwy-0007ps-00@the-village.bc.nu> (raw)
In-Reply-To: <200106282305.BAA17845@harpo.it.uu.se> from "Mikael Pettersson" at Jun 29, 2001 01:05:06 AM
> Here I have to disagree with you Alan. When you pass "-march=i686" to
> gcc, you are _not_ saying "generate code for a CPUID family 6 CPU".
> "-march=i686" actually means "target an Intel P6 family chip, given
> what we currently know about them". The gcc info pages don't talk
Which is fine. The Pentium Pro manual explicitly states that cmov may go
away. So it is not based on what we know about the CPU, its based on not
reading the documentation.
It's a bug. -march=i6868 does not 'target an Intel P6 family chip, ...'
It happens to work because the error in reading the docs was never triggered
by intel removing cmov from a cpu as the reserved the right to do
Alan
next prev parent reply other threads:[~2001-06-28 23:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-28 23:05 Mikael Pettersson
2001-06-28 23:11 ` Alan Cox [this message]
2001-06-29 8:02 ` Bernd Schmidt
2001-06-29 9:51 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2001-06-29 2:52 Frank Zhu (Shanghai)
2001-06-28 18:39 PROBLEM:Illegal instruction when mount nfs file systems using cyr ixIII Bernd Schmidt
2001-06-28 19:42 ` PROBLEM:Illegal instruction when mount nfs file systems using Alan Cox
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=E15Fkwy-0007ps-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=FrankZhu@viatech.com.cn \
--cc=bernds@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
/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
all inboxes | Powered by JetHome®