> > 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
>
> Pedantically you may be right, but it's not a very useful
On Fri, 29 Jun 2001, Alan Cox wrote:
> > 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".
On Fri, 29 Jun 2001, Alan Cox wrote:
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
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
Pedantically you may be right, but it's not a very useful interpretation
-
From: Alan Cox [mailto:[EMAIL PROTECTED]]
Sent: 2001年6月29日 7:12
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: PROBLEM:Illegal instruction when mount nfs file systems using
> Here I have to disagree with you A
> 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.
On Thu, 28 Jun 2001 20:42:09 +0100 (BST), Alan Cox wrote:
>> > Intel specifically state that you cannot use CMOV without checking
>> > for it. Its actually a gcc/binutils tool bug. The CPU is right.
>>
>> How is that a gcc bug? You tell the compiler to generate cmov, you run
>> it on a CPU
> > Intel specifically state that you cannot use CMOV without checking
> > for it. Its actually a gcc/binutils tool bug. The CPU is right.
>
> How is that a gcc bug? You tell the compiler to generate cmov, you run
> it on a CPU that doesn't have it, you get what you deserve. There's
> really
-
From: Alan Cox [mailto:[EMAIL PROTECTED]]
Sent: 2001年6月29日 7:12
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: PROBLEM:Illegal instruction when mount nfs file systems using
Here I have to disagree with you Alan
Intel specifically state that you cannot use CMOV without checking
for it. Its actually a gcc/binutils tool bug. The CPU is right.
How is that a gcc bug? You tell the compiler to generate cmov, you run
it on a CPU that doesn't have it, you get what you deserve. There's
really nothing
On Thu, 28 Jun 2001 20:42:09 +0100 (BST), Alan Cox wrote:
Intel specifically state that you cannot use CMOV without checking
for it. Its actually a gcc/binutils tool bug. The CPU is right.
How is that a gcc bug? You tell the compiler to generate cmov, you run
it on a CPU that doesn't
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
> The problem is that VIA Cyrix III announces itself (via CPUID)
> as a "family 6" processor, i.e. i686 compatible. This is not
> completely accurate, since it doesn't implement the conditional
> move instruction. [Yeah, I know there's a CPUID feature flag for
Intel specifically state that you
On Wed, 27 Jun 2001 17:42:01 +0800, Frank Zhu wrote:
>I use a PIII machine as the server and cyrixIII machine as the client.The
>kernel is 2.4.5.The distribute is red hat 7.1
>when i mount the nfs file system at the client it failed.The core file is
>created.using the gdb it report :
>Program
hi:
I use a PIII machine as the server and cyrixIII machine as the client.The
kernel is 2.4.5.The distribute is red hat 7.1
when i mount the nfs file system at the client it failed.The core file is
created.using the gdb it report :
Program terminated with signal 4(SIGILL),Illegal instruction
#0
hi:
I use a PIII machine as the server and cyrixIII machine as the client.The
kernel is 2.4.5.The distribute is red hat 7.1
when i mount the nfs file system at the client it failed.The core file is
created.using the gdb it report :
Program terminated with signal 4(SIGILL),Illegal instruction
#0
On Wed, 27 Jun 2001 17:42:01 +0800, Frank Zhu wrote:
I use a PIII machine as the server and cyrixIII machine as the client.The
kernel is 2.4.5.The distribute is red hat 7.1
when i mount the nfs file system at the client it failed.The core file is
created.using the gdb it report :
Program
The problem is that VIA Cyrix III announces itself (via CPUID)
as a family 6 processor, i.e. i686 compatible. This is not
completely accurate, since it doesn't implement the conditional
move instruction. [Yeah, I know there's a CPUID feature flag for
Intel specifically state that you cannot
18 matches
Mail list logo
