public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebuddington at wesleyan dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/37179]  New: gcc emits bad opcode 'ffreep'
Date: Wed, 20 Aug 2008 19:17:00 -0000	[thread overview]
Message-ID: <bug-37179-2749@http.gcc.gnu.org/bugzilla/> (raw)

The vortex86sx claims to be 486-compliant, but it gives "Illegal Instruction"
on ffreep.

GCC uses ffreep when compiling many pieces of software, rendering them unusable
on this processor.

I do not see any way to explicitly blacklist the opcode, and setting -march to
i486, i386, or native does not avoid the problem.

Could this be added as an architecture, or is there an existing solution that
I'm missing?


-- 
           Summary: gcc emits bad opcode 'ffreep'
           Product: gcc
           Version: 4.3.0
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P3
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: ebuddington at wesleyan dot edu
 GCC build triplet: vortex86-pc-linux
  GCC host triplet: vortex86-pc-linux
GCC target triplet: vortex86-pc-linux


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37179


             reply	other threads:[~2008-08-20 19:17 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-20 19:17 ebuddington at wesleyan dot edu [this message]
2008-08-20 19:19 ` [Bug target/37179] " pinskia at gcc dot gnu dot org
2008-08-20 19:20 ` pinskia at gcc dot gnu dot org
2008-08-20 19:20 ` pinskia at gcc dot gnu dot org
2009-05-07 17:54 ` sascha-web-gcc dot gnu dot org at silbe dot org
2009-05-07 18:00 ` sascha-web-gcc dot gnu dot org at silbe dot org
2009-05-07 20:37 ` ubizjak at gmail dot com
2009-05-10 10:07 ` sascha-web-gcc dot gnu dot org at silbe dot org
2009-05-10 14:28 ` ubizjak at gmail dot com
2009-05-10 17:12 ` sascha-web-gcc dot gnu dot org at silbe dot org
2009-05-10 17:51 ` ubizjak at gmail dot com
2009-05-10 18:05 ` sascha-web-gcc dot gnu dot org at silbe dot org
2009-05-10 20:56 ` ubizjak at gmail dot com
2009-05-10 21:22 ` sascha-web-gcc dot gnu dot org at silbe dot org
2009-05-10 22:00 ` ubizjak at gmail dot com
2009-05-12 12:08 ` ubizjak at gmail dot com
2009-05-12 16:33 ` hjl at gcc dot gnu dot org
2009-05-13 10:06 ` uros at gcc dot gnu dot org
2009-05-14  8:23 ` uros at gcc dot gnu dot org
2009-05-14  8:25 ` ubizjak at gmail dot com

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=bug-37179-2749@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).