From: "Richard Guenther" <richard.guenther@gmail.com>
To: Alok kataria <alokkataria1@gmail.com>
Cc: gcc@gcc.gnu.org, linux-assembly@vger.kernel.org
Subject: Re: "Error: suffix or operands invalid for `push'" on 64bit boxes
Date: Thu, 22 Feb 2007 13:23:51 +0100 [thread overview]
Message-ID: <84fc9c000702220423k22066ea1vcc629b74851ae931@mail.gmail.com> (raw)
In-Reply-To: <35f686220702220350sa328106v6ad9f4a5e42f1dd7@mail.gmail.com>
On 2/22/07, Alok kataria <alokkataria1@gmail.com> wrote:
> Hi,
>
> I was trying some inline assembly with gcc.
>
> Running the assembly program on 64 bit system ( with 64bit gcc
> version) gives errors of the form
>
> /tmp/cc28kO9v.s: Assembler messages:
> /tmp/cc28kO9v.s:57: Error: suffix or operands invalid for `push'
This is off topic here, please use gcc-help@gcc.gnu.org for this kind
of questions.
Your assembly statements are not valid 64bit asm but only work on 32bit.
Richard.
prev parent reply other threads:[~2007-02-22 12:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-22 11:50 "Error: suffix or operands invalid for `push'" on 64bit boxes Alok kataria
2007-02-22 12:17 ` Andrew Haley
2007-02-22 12:23 ` Richard Guenther [this message]
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=84fc9c000702220423k22066ea1vcc629b74851ae931@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=alokkataria1@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=linux-assembly@vger.kernel.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).