From: Alan Modra <amodra@bigpond.net.au>
To: Mikulas Patocka <mikulas@artax.karlin.mff.cuni.cz>
Cc: binutils@sources.redhat.com, bug-binutils@gnu.org
Subject: Re: 16-bit code in GAS
Date: Fri, 15 Aug 2003 15:25:00 -0000 [thread overview]
Message-ID: <20030815141919.GE27145@bubble.sa.bigpond.net.au> (raw)
In-Reply-To: <Pine.LNX.4.44.0308151532490.25593-100000@artax.karlin.mff.cuni.cz>
On Fri, Aug 15, 2003 at 03:44:13PM +0200, Mikulas Patocka wrote:
> The resulting instruction should have prefixes 66 and 67 and should have
> 32-bit address.
It certainly looks buggy. I would have expected that gas generate just
the data prefix and trim the address to 16 bit. Instead we get a 32 bit
address inserted into the instruction.
> How can I write 32-bit code that runs in a segment with default operand
> size 16 (without 'D' bit set)?
.code16
addr32 movl $0x12345678, 0xabcdef01
--
Alan Modra
IBM OzLabs - Linux Technology Centre
next prev parent reply other threads:[~2003-08-15 15:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-15 13:44 Mikulas Patocka
2003-08-15 15:25 ` Alan Modra [this message]
2003-08-15 16:05 ` Mikulas Patocka
2003-08-15 18:08 ` Ian Lance Taylor
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=20030815141919.GE27145@bubble.sa.bigpond.net.au \
--to=amodra@bigpond.net.au \
--cc=binutils@sources.redhat.com \
--cc=bug-binutils@gnu.org \
--cc=mikulas@artax.karlin.mff.cuni.cz \
/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).