public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: Alan Modra <amodra@bigpond.net.au>,
	Andreas Schwab <schwab@suse.de>,
	binutils@sources.redhat.com, Stefan Reinauer <stepan@suse.de>
Subject: Re: 64bit bfd_vma vs 32bit address space in linker
Date: Tue, 08 Apr 2003 06:53:00 -0000	[thread overview]
Message-ID: <20030408065256.GF24435@rembrandt.csv.ica.uni-stuttgart.de> (raw)
In-Reply-To: <orsmsth5ep.fsf@free.redhat.lsd.ic.unicamp.br>

Alexandre Oliva wrote:
> On Apr  8, 2003, Alan Modra <amodra@bigpond.net.au> wrote:
> 
> > Without looking in detail at the code, I believe that bits_per_address
> > is exactly the right thing to use to implement the (currently missing
> > when BFD64) linker address wrap.
> 
> I'm afraid it isn't.  Consider 32-bit code (say o32) running on a
> 64-bit architecture (MIPS III).  You do want to truncate addresses to
> 32 bits, since the ABI mandates 32-bit addresses, but bits_per_address
> will return 64.

Looks like MIPS gets it wrong in cpu-mips.c. Other architectures (ia64)
use different bfd_mach_* vectors for this purpose.


Thiemo

      parent reply	other threads:[~2003-04-08  6:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-04 15:46 Andreas Schwab
2003-04-08  0:58 ` Alan Modra
2003-04-08  2:47   ` Alexandre Oliva
2003-04-08  5:17     ` Alan Modra
2003-04-08  6:25       ` Alexandre Oliva
2003-04-08  6:45         ` Alan Modra
2003-04-08  6:55           ` Alexandre Oliva
2003-04-08  9:49             ` Alan Modra
2003-04-08 10:13               ` Alexandre Oliva
2003-04-08  7:28           ` Andreas Jaeger
2003-04-08  8:53             ` Alan Modra
2003-04-08  6:53         ` Thiemo Seufer [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=20030408065256.GF24435@rembrandt.csv.ica.uni-stuttgart.de \
    --to=ica2_ts@csv.ica.uni-stuttgart.de \
    --cc=amodra@bigpond.net.au \
    --cc=aoliva@redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=schwab@suse.de \
    --cc=stepan@suse.de \
    /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).