public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@zembu.com>
To: dicarlo@apegate.roma1.infn.it
Cc: binutils@sourceware.cygnus.com
Subject: Re: (BFD): Non-byte addressing possible?
Date: Fri, 14 Jul 2000 10:27:00 -0000	[thread overview]
Message-ID: <20000714172729.5605.qmail@daffy.airs.com> (raw)
In-Reply-To: <396F21DC.E28933B@apemaia.roma1.infn.it>

   Date: Fri, 14 Jul 2000 16:21:16 +0200
   From: Di Carlo Federico <dicarlo@apegate.roma1.infn.it>

   We are trying to port all binutils to our parallel-architecture machine.

   This architecture demands non per-byte addressing.
   In fact we have to provide address via a 32 bit bus referring 16 byte (a
   word, in this machine) with an address.

   For example if address 0x8000 is address 0x4000 for memory controller
   then address 0x8001 is address 0x4010 . So subseguent addresses refers
   to 128 different bits in memory.

   As far as we discovered it's not possible to force binutils (just BFD
   ELF support, we guess, due to relocs) to support this feature, so we
   think we'll have to do very strange magic translation at reloc/link
   time.

   Are there any features we didn't see or any back-end already using such
   an addressing we could study?

See the tic54x and the octets_per_byte code.  Perhaps it will help.

Ian

  parent reply	other threads:[~2000-07-14 10:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-14  7:21 Di Carlo Federico
2000-07-14  8:11 ` gprof: bb counts John Levon
2000-07-14 10:27 ` Ian Lance Taylor [this message]
2000-07-17  5:32 (BFD): Non-byte addressing possible? Timothy Wall

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=20000714172729.5605.qmail@daffy.airs.com \
    --to=ian@zembu.com \
    --cc=binutils@sourceware.cygnus.com \
    --cc=dicarlo@apegate.roma1.infn.it \
    /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).