From: David Korn <dkorn@pixelpower.com>
To: crossgcc@sources.redhat.com
Subject: RE: Invalid Operands with Inline assembly
Date: Thu, 26 Oct 2000 04:46:00 -0000 [thread overview]
Message-ID: <718D38CAB6E0D011B2C90060970C28A556FC80@exchangeserver.pixelpower.com> (raw)
>I am attempting to embed inline assembly into my C code but during the
>compilation, I keep getting the error "invalid operands for opcode".
>Here is one of my lines:
>
>asm("mov %r14, %r15");
I've found (on PPC; it might apply to SH also) that you can't put a
space between the two operands. gas expects the entire operand list to
be in one field, the space acts as a separator, and it parses what you've
typed as
mov %r14,
followed by a comment field that contains the text "%r15". So try again
without the space. What that other guy said about %-signs might matter too.
DaveK
--
SEAL Team 6 World Trade Center Serbian Cocaine [Hello to all my fans
in domestic surveillance] cracking KGB nuclear arrangements CIA
counter-intelligence smuggle fissionable ammunition SDI
------
Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com
next reply other threads:[~2000-10-26 4:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-26 4:46 David Korn [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-10-31 16:59 Stan Katz
2000-11-01 6:09 ` Sobhy Gad
2000-11-01 13:56 ` Robert Floyd
[not found] <A7FF74878269D411A56F00A0C9ACE7CE75A6@golden.ctc-control.com>
2000-10-31 14:46 ` Robert Floyd
2000-10-27 13:37 Stan Katz
2000-10-26 12:12 Stan Katz
2000-10-27 11:01 ` Robert Floyd
[not found] <A7FF74878269D411A56F00A0C9ACE7CE75A2@golden.ctc-control.com>
2000-10-26 11:39 ` Robert Floyd
2000-10-25 14:23 Robert Floyd
2000-10-26 0:12 ` Keith Wright
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=718D38CAB6E0D011B2C90060970C28A556FC80@exchangeserver.pixelpower.com \
--to=dkorn@pixelpower.com \
--cc=crossgcc@sources.redhat.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: 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).