public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* RE: other/8311: Legal intel instructions being flagged as illegal
@ 2002-10-22 13:36 Tomás Palmer
0 siblings, 0 replies; 2+ messages in thread
From: Tomás Palmer @ 2002-10-22 13:36 UTC (permalink / raw)
To: nobody; +Cc: gcc-prs
The following reply was made to PR other/8311; it has been noted by GNATS.
From: =?iso-8859-1?Q?Tom=E1s_Palmer?= <Tpalmer@widevine.com>
To: "'zack@gcc.gnu.org'" <zack@gcc.gnu.org>, "'gcc-bugs@gcc.gnu.org'"
<gcc-bugs@gcc.gnu.org>, "'gcc-prs@gcc.gnu.org'" <gcc-prs@gcc.gnu.org>,
"'nobody@gcc.gnu.org'" <nobody@gcc.gnu.org>, =?iso-8859-1?Q?Tom=E1s_Pa?=
=?iso-8859-1?Q?lmer?= <Tpalmer@widevine.com>, "'gcc-gnats@gcc.gnu.org'"
<gcc-gnats@gcc.gnu.org>
Cc:
Subject: RE: other/8311: Legal intel instructions being flagged as illegal
Date: Tue, 22 Oct 2002 13:32:12 -0700
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C27A0A.1A4709C0
Content-Type: text/plain;
charset="iso-8859-1"
Thank you, very much.
I will change my code.
-----Original Message-----
From: zack@gcc.gnu.org [mailto:zack@gcc.gnu.org]
Sent: Tuesday, October 22, 2002 1:21 PM
To: gcc-bugs@gcc.gnu.org; gcc-prs@gcc.gnu.org; nobody@gcc.gnu.org;
tpalmer@widevine.com
Subject: Re: other/8311: Legal intel instructions being flagged as
illegal
Synopsis: Legal intel instructions being flagged as illegal
State-Changed-From-To: open->closed
State-Changed-By: zack
State-Changed-When: Tue Oct 22 13:20:42 2002
State-Changed-Why:
GCC does not attempt to interpret the text of an asm() statement, beyond
processing %-substitutions for operands. The error message you quoted came
from the assembler.
The instruction mnemonics "pushfd" and "popfd" are valid only in Intel
syntax. In its default mode, GAS uses AT&T syntax, in which these opcodes
are spelled "pushf" and "popf" respectively. You can either change your
code to use these, or (with sufficiently recent versions of GCC and GAS) you
can use the -masm=intel command line switch.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&p
r=8311
------_=_NextPart_001_01C27A0A.1A4709C0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>RE: other/8311: Legal intel instructions being flagged as =
illegal</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2>Thank you, very much.</FONT>
<BR><FONT SIZE=3D2>I will change my code.</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: zack@gcc.gnu.org [<A =
HREF=3D"mailto:zack@gcc.gnu.org">mailto:zack@gcc.gnu.org</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Tuesday, October 22, 2002 1:21 PM</FONT>
<BR><FONT SIZE=3D2>To: gcc-bugs@gcc.gnu.org; gcc-prs@gcc.gnu.org; =
nobody@gcc.gnu.org;</FONT>
<BR><FONT SIZE=3D2>tpalmer@widevine.com</FONT>
<BR><FONT SIZE=3D2>Subject: Re: other/8311: Legal intel instructions =
being flagged as</FONT>
<BR><FONT SIZE=3D2>illegal</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>Synopsis: Legal intel instructions being flagged as =
illegal</FONT>
</P>
<P><FONT SIZE=3D2>State-Changed-From-To: open->closed</FONT>
<BR><FONT SIZE=3D2>State-Changed-By: zack</FONT>
<BR><FONT SIZE=3D2>State-Changed-When: Tue Oct 22 13:20:42 2002</FONT>
<BR><FONT SIZE=3D2>State-Changed-Why:</FONT>
<BR><FONT SIZE=3D2> GCC does not attempt to interpret =
the text of an asm() statement, beyond processing %-substitutions for =
operands. The error message you quoted came from the =
assembler.</FONT></P>
<P><FONT SIZE=3D2> </FONT>
<BR><FONT SIZE=3D2> The instruction mnemonics =
"pushfd" and "popfd" are valid only in Intel =
syntax. In its default mode, GAS uses AT&T syntax, in which =
these opcodes are spelled "pushf" and "popf" =
respectively. You can either change your code to use these, or =
(with sufficiently recent versions of GCC and GAS) you can use the =
-masm=3Dintel command line switch.</FONT></P>
<P><FONT SIZE=3D2><A =
HREF=3D"http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=3Dview%20audit-trail&=
database=3Dgcc&pr=3D8311" =
TARGET=3D"_blank">http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=3Dview%20au=
dit-trail&database=3Dgcc&pr=3D8311</A></FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01C27A0A.1A4709C0--
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: other/8311: Legal intel instructions being flagged as illegal
@ 2002-10-22 13:20 zack
0 siblings, 0 replies; 2+ messages in thread
From: zack @ 2002-10-22 13:20 UTC (permalink / raw)
To: gcc-bugs, gcc-prs, nobody, tpalmer
Synopsis: Legal intel instructions being flagged as illegal
State-Changed-From-To: open->closed
State-Changed-By: zack
State-Changed-When: Tue Oct 22 13:20:42 2002
State-Changed-Why:
GCC does not attempt to interpret the text of an asm() statement, beyond processing %-substitutions for operands. The error message you quoted came from the assembler.
The instruction mnemonics "pushfd" and "popfd" are valid only in Intel syntax. In its default mode, GAS uses AT&T syntax, in which these opcodes are spelled "pushf" and "popf" respectively. You can either change your code to use these, or (with sufficiently recent versions of GCC and GAS) you can use the -masm=intel command line switch.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8311
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2002-10-22 20:36 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-10-22 13:36 other/8311: Legal intel instructions being flagged as illegal Tomás Palmer
-- strict thread matches above, loose matches on Subject: below --
2002-10-22 13:20 zack
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).