public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: tpalmer@widevine.com
To: gcc-gnats@gcc.gnu.org
Subject: ada/8311: Legal intel instructions being flagged as illegal
Date: Tue, 22 Oct 2002 13:06:00 -0000	[thread overview]
Message-ID: <20021022200439.31453.qmail@sources.redhat.com> (raw)


>Number:         8311
>Category:       ada
>Synopsis:       Legal intel instructions being flagged as illegal
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          rejects-legal
>Submitter-Id:   net
>Arrival-Date:   Tue Oct 22 13:06:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Tomas Palmer
>Release:        3.2
>Organization:
>Environment:
$ gcc -v
Reading specs from /usr/lib/gcc-lib/i686-pc-cygwin/3.2/specs
Configured with: /netrel/src/gcc-3.2-1/configure --enable-languages=c,c++,f77,java --enable-libgcj --enable-threads=posi
x --with-system-zlib --enable-nls --without-included-gettext --enable-interpreter --disable-sjlj-exceptions --disable-ve
rsion-specific-runtime-libs --enable-shared --build=i686-pc-linux --host=i686-pc-cygwin --target=i686-pc-cygwin --enable
-haifa --prefix=/usr --exec-prefix=/usr --sysconfdir=/etc --libdir=/usr/lib --includedir=/nonexistent/include --libexecd
ir=/usr/sbin
Thread model: posix
gcc version 3.2 20020818 (prerelease)
>Description:
Command line switches
$ gcc -march=pentium -mcpu=pentium cpuid.cpp

... Error: no such instruction: `pushfd '
... Error: no such instruction: `popfd '

These are legal intel instructions and supported both by intel inline and microsoft inline 
>How-To-Repeat:
$ gcc -march=pentium -mcpu=pentium cpuid.cpp
>Fix:
Add these instructions to legal instruction set for 486 and above
>Release-Note:
>Audit-Trail:
>Unformatted:


                 reply	other threads:[~2002-10-22 20:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20021022200439.31453.qmail@sources.redhat.com \
    --to=tpalmer@widevine.com \
    --cc=gcc-gnats@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).