Re: optimization/8525: cmov instruction used with i686

Re: optimization/8525: cmov instruction used with i686

[paolo]

Synopsis: cmov instruction used with i686

State-Changed-From-To: feedback->closed
State-Changed-By: paolo
State-Changed-When: Mon Nov 11 01:09:02 2002
State-Changed-Why:
    As Eric noticed, duplicate of target/8243, as such not a bug
    according to Rth.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8525

Re: optimization/8525: cmov instruction used with i686

[Devin Bayer]

The following reply was made to PR optimization/8525; it has been noted by GNATS.

From: Devin Bayer <gcc@elektrono.com>
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
  gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: optimization/8525: cmov instruction used with i686
Date: Mon, 11 Nov 2002 04:06:37 -0500

 paolo@gcc.gnu.org wrote:
   >     Is this still an issue with recent gcc releases (3.x, x>= 0)?
 
 I have not tested it myself, but Daniel Jacobowitz claims gcc version
 3.2 still has this problem and I have no reason to believe differently.
 
 Here is a link to the post:
 http://groups.google.com/groups?selm=20021105142740.GA20877%40nevyn.them.org
 
 
 

Re: optimization/8525: cmov instruction used with i686

[paolo]

Synopsis: cmov instruction used with i686

State-Changed-From-To: open->feedback
State-Changed-By: paolo
State-Changed-When: Mon Nov 11 00:34:40 2002
State-Changed-Why:
    Is this still an issue with recent gcc releases (3.x, x>= 0)?
    2.95.x is very old and not maintained anymore.
    Thanks, Paolo.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8525

optimization/8525: cmov instruction used with i686

[gcc]

>Number:         8525
>Category:       optimization
>Synopsis:       cmov instruction used with i686
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Sun Nov 10 22:56:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     gcc@elektrono.com
>Release:        2.95.4
>Organization:
>Environment:
Debian GNU/Linux 3.0
Linux 2.4.19
Via C3 Processor
>Description:
When gcc compiles code for i686's it utilizes the cmov instruction, which is not part of the required i686 instruction set according to intel's specification.  This causes headaches because a dynamic linker will try to use i686 optimized binaries with the i686 processor and they will generate "Illegal Instruction" errors.

Either the code detecting the processor in the dynamic linker needs to be hacked to report i686 processors without the cmov instruction as i586's or gcc needs to not use the cmov instruction when asked to produce i686 binaries.
In all seriousness, does the gcc group feel that the cpu detection code should follow gcc's broken implementation?

>From my perspective this is a big problem. I see it pop up in bugs, mailing list, and USENET posts far too often.  People are discouraged from combining Linux and Via C3 Processors. This bug also recently broke SSH on my server (See Debian Bug #164766).

This problem will only get worse as more i686-optimized binaries are produced.  There is no easy way to just use '-march=i586' when using a binary distribution like Debian or a commercial product with no source available.

I hope I didn't come off too demanding in this bug report. I really appreciate all the work you guys put into gcc.  It just seems this is only a case of purposely not following the specification that's breaking things and that is one of the worst kind of bugs.  I strongly believe in spec. compliance, because without it interoperability is twice as hard.  So please make the many C3-owner/Linux-users lives easier and at least by default don't use cmov.
>How-To-Repeat:

>Fix:
When compiling code with -march=i686 do not use the cmov instruction by default.  The use of cmov could be requested with -fcmov or something similar.
>Release-Note:
>Audit-Trail:
>Unformatted: