public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Tomás Palmer" <Tpalmer@widevine.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: RE: target/8272: Unrecognized x86 instructions
Date: Tue, 22 Oct 2002 10:06:00 -0000 [thread overview]
Message-ID: <20021022170602.30736.qmail@sources.redhat.com> (raw)
The following reply was made to PR target/8272; it has been noted by GNATS.
From: =?iso-8859-1?Q?Tom=E1s_Palmer?= <Tpalmer@widevine.com>
To: "'rth@gcc.gnu.org'" <rth@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: target/8272: Unrecognized x86 instructions
Date: Tue, 22 Oct 2002 09:58:51 -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_01C279EC.4BF69850
Content-Type: text/plain;
charset="iso-8859-1"
I disagree. While I might buy that it is the fact that the default of the
compiler is 386 on an Intel86 platform rather than 486+ might prevent these
specific instructions. I am checking out that theory today now that I have
documents for Gcc.
The ASM instructions are correct as sent to you and assemble in-line with
both Microsoft,Intel and other compilers in both Intel and ATT format.
If my theory about the cpu flag does not address this issue then I am
re-filing this bug and hope it gets assigned to someone with some ability to
properly verify a test scenario rather than just guess.
-----Original Message-----
From: rth@gcc.gnu.org [mailto:rth@gcc.gnu.org]
Sent: Tuesday, October 22, 2002 12:06 AM
To: gcc-bugs@gcc.gnu.org; gcc-prs@gcc.gnu.org; nobody@gcc.gnu.org;
tpalmer@widevine.com
Subject: Re: target/8272: Unrecognized x86 instructions
Synopsis: Unrecognized x86 instructions
State-Changed-From-To: open->closed
State-Changed-By: rth
State-Changed-When: Tue Oct 22 00:06:05 2002
State-Changed-Why:
No test case. And it's almost certainly a problem of
invalid inline assembly rather than a compiler bug.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&p
r=8272
------_=_NextPart_001_01C279EC.4BF69850
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: target/8272: Unrecognized x86 instructions</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2>I disagree. While I might buy that it is the fact =
that the default of the compiler is 386 on an Intel86 platform rather =
than 486+ might prevent these specific instructions. I am checking out =
that theory today now that I have documents for Gcc.</FONT></P>
<P><FONT SIZE=3D2>The ASM instructions are correct as sent to you and =
assemble in-line with both Microsoft,Intel and other compilers in both =
Intel and ATT format.</FONT></P>
<P><FONT SIZE=3D2>If my theory about the cpu flag does not address this =
issue then I am re-filing this bug and hope it gets assigned to someone =
with some ability to properly verify a test scenario rather than just =
guess.</FONT></P>
<BR>
<BR>
<BR>
<BR>
<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: rth@gcc.gnu.org [<A =
HREF=3D"mailto:rth@gcc.gnu.org">mailto:rth@gcc.gnu.org</A>] </FONT>
<BR><FONT SIZE=3D2>Sent: Tuesday, October 22, 2002 12:06 AM</FONT>
<BR><FONT SIZE=3D2>To: gcc-bugs@gcc.gnu.org; gcc-prs@gcc.gnu.org; =
nobody@gcc.gnu.org; tpalmer@widevine.com</FONT>
<BR><FONT SIZE=3D2>Subject: Re: target/8272: Unrecognized x86 =
instructions</FONT>
</P>
<P><FONT SIZE=3D2>Synopsis: Unrecognized x86 instructions</FONT>
</P>
<P><FONT SIZE=3D2>State-Changed-From-To: open->closed</FONT>
<BR><FONT SIZE=3D2>State-Changed-By: rth</FONT>
<BR><FONT SIZE=3D2>State-Changed-When: Tue Oct 22 00:06:05 2002</FONT>
<BR><FONT SIZE=3D2>State-Changed-Why:</FONT>
<BR><FONT SIZE=3D2> No test case. And it's =
almost certainly a problem of</FONT>
<BR><FONT SIZE=3D2> invalid inline assembly rather =
than a compiler bug.</FONT>
</P>
<P><FONT SIZE=3D2><A =
HREF=3D"http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=3Dview%20audit-trail&=
database=3Dgcc&pr=3D8272" =
TARGET=3D"_blank">http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=3Dview%20au=
dit-trail&database=3Dgcc&pr=3D8272</A></FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01C279EC.4BF69850--
next reply other threads:[~2002-10-22 17:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-22 10:06 Tomás Palmer [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-22 0:06 rth
2002-10-17 16:26 tpalmer
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=20021022170602.30736.qmail@sources.redhat.com \
--to=tpalmer@widevine.com \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).