public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@zembu.com>
To: geoffk@cygnus.com
Cc: ulfc@calypso.engr.sgi.com, ac131313@cygnus.com,
	alan@linuxcare.com.au, binutils@sourceware.cygnus.com,
	gdb-patches@sourceware.cygnus.com
Subject: Re: [rfc] For mips, sign-extended ecoff offsets
Date: Mon, 19 Jun 2000 20:41:00 -0000	[thread overview]
Message-ID: <20000620034102.18244.qmail@daffy.airs.com> (raw)
In-Reply-To: <200006200307.UAA10516@localhost.cygnus.com>

   Date: Mon, 19 Jun 2000 20:07:59 -0700
   From: Geoff Keating <geoffk@cygnus.com>

   > From: Ulf Carlsson <ulfc@calypso.engr.sgi.com>
   > Date: Mon, 19 Jun 2000 18:45:44 -0700 (PDT)

   > On a 64-bit MIPS processor 32-bit addresses are of course sign
   > extended, but this shouldn't concern the 32-bit BFD backend for MIPS
   > in any way.  Whether we sign extend the addresses or not shouldn't
   > make any difference except in our internal representation of the
   > bfd_vma.  I may be wrong though!

   The 64-bit MIPS machines often use the 32-bit ELF format, typically
   because they have 32-bit memory addresses (I forget whether trying to
   access 0x0000000087654321 gives you 0xffffffff87654321 or a trap).

I think the real reason this happens is historical--because we didn't
have a 64-bit MIPS format when we started supporting 64-bit MIPS
chips.  I don't think there is any particularly legitimate reason to
use a 32-bit format for a 64-bit chip.

Ian

  reply	other threads:[~2000-06-19 20:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-19  5:14 Andrew Cagney
2000-06-19  8:48 ` Alan Modra
2000-06-19 18:18   ` Andrew Cagney
2000-06-19 18:47     ` Ulf Carlsson
2000-06-19 18:57       ` Alan Modra
2000-06-19 19:16       ` Andrew Cagney
2000-06-19 20:08       ` Geoff Keating
2000-06-19 20:41         ` Ian Lance Taylor [this message]
2000-06-25 14:13           ` Ralf Baechle
     [not found]         ` <14670.59816.517716.492387@calypso.engr.sgi.com>
2000-06-19 21:30           ` Geoff Keating
2000-06-19 18:50     ` Alan Modra
2000-06-19 19:23       ` Andrew Cagney
2000-06-19 20:39       ` Ian Lance Taylor
2000-06-23  0:28         ` Andrew Cagney
2000-06-23  9:48           ` Ian Lance Taylor
2000-07-03 23:47             ` Andrew Cagney

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=20000620034102.18244.qmail@daffy.airs.com \
    --to=ian@zembu.com \
    --cc=ac131313@cygnus.com \
    --cc=alan@linuxcare.com.au \
    --cc=binutils@sourceware.cygnus.com \
    --cc=gdb-patches@sourceware.cygnus.com \
    --cc=geoffk@cygnus.com \
    --cc=ulfc@calypso.engr.sgi.com \
    /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).