From: Mark P Anderson <manders1@csc.com>
To: binutils@sourceware.org
Subject: GAS Relocation and Relaxation of 24-bit Address
Date: Wed, 12 Dec 2007 18:11:00 -0000 [thread overview]
Message-ID: <OFA540F459.5ADB769F-ON852573AF.0063606F-852573AF.0063E72E@csc.com> (raw)
I'm working on a gas port for a machine that has variable length
instructions that are multiples of 1 byte (8-bits). The address,
both PC relative and absolute, can be 8-bits, 16-bits or 24-bits
in length that reside in bytes past the opcode bytes.
From looking at the bfd.c code it seems like addresses have to
be either 16-bits or 32-bits when reading or writing to the bfd.
Am I reading the code right? Am I going to have a big problem
trying to read and write 24-bit addresses? Am I going to have
problems with variable length, byte-oriented instruction encoding?
next reply other threads:[~2007-12-12 18:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-12 18:11 Mark P Anderson [this message]
2007-12-12 18:20 ` DJ Delorie
2007-12-12 20:00 ` Mark P Anderson
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=OFA540F459.5ADB769F-ON852573AF.0063606F-852573AF.0063E72E@csc.com \
--to=manders1@csc.com \
--cc=binutils@sourceware.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).