public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: zack@gcc.gnu.org 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 Date: Tue, 22 Oct 2002 13:20:00 -0000 [thread overview] Message-ID: <20021022202043.4850.qmail@sources.redhat.com> (raw) 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
next reply other threads:[~2002-10-22 20:20 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-10-22 13:20 zack [this message] 2002-10-22 13:36 Tomás Palmer
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=20021022202043.4850.qmail@sources.redhat.com \ --to=zack@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ --cc=tpalmer@widevine.com \ /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: linkBe 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).