From: Andreas Schwab <schwab@suse.de>
To: kieft_brian@si.com
Cc: linux-assembly@vger.kernel.org, binutils@sources.redhat.com
Subject: Re: wrong opcode?
Date: Fri, 14 Jun 2002 22:18:47 +0200 [thread overview]
Message-ID: <je4rg5d36g.fsf@sykes.suse.de> (raw)
In-Reply-To: <004E42C8.C21188@si.com> (<kieft_brian@si.com>'s message of "Fri, 14 Jun 2002 13:27:06 -0400")
<kieft_brian@si.com> writes:
|> I curious as to why the code generated for these two move.w commands is
|> completely different. In the first assembly I used two variables (one equal to 0
|> and the other equal to 8). I tried doing a move using the variables added
|> together as my offset to register A1 and managed to get 33B9 0000 0000 0170 0000
|> 0008. When I simply put an 8 in instead of the variables, I got the correct
|> code. 3379 0000 0000 0008. Any ideas??????
|>
|> I'm using gnu as on a pc-cygwin system with a m68k target.
|>
|>
|> 3901 034a 0000 0008 .DC.L C_WCP1_MSG_PARM
|> 3902 034e 0000 0000 .DC.L HWPN_PARM_OFS
|> 3903 0352 33B9 0000 MOVE.W SYS_SYS_VERS_W,C_WCP_MSG_PARM+HWPN_PARM_OFS(%A1)
|> 3903 0000 0170
|> 3903 0000 0008
The other opcode is not wrong, it just uses the 32bit offset form. How
are C_WCP_MSG_PARM and HWPN_PARM_OFS defined? Please provide a complete,
self-contained test case.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
-
To unsubscribe from this list: send the line "unsubscribe linux-assembly" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2002-06-14 20:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-14 17:27 wrong opcode? kieft_brian
2002-06-14 19:06 ` Peter Barada
2002-06-14 20:18 ` Andreas Schwab [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=je4rg5d36g.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=binutils@sources.redhat.com \
--cc=kieft_brian@si.com \
--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