public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Thiemo Seufer <ths@networkno.de>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Eric Christopher <erchrist@cisco.com>,
	newlib@sources.redhat.com, binutils@sources.redhat.com,
	cgd@broadcom.com
Subject: Re: [patch] adjust libgloss addresses for 64-bit
Date: Fri, 15 Apr 2005 11:28:00 -0000	[thread overview]
Message-ID: <20050415112755.GA21496@hattusa.textio> (raw)
In-Reply-To: <Pine.LNX.4.61L.0504151124070.23166@blysk.ds.pg.gda.pl>

Maciej W. Rozycki wrote:
[snip]
> > I think la should load a proper address for 32bit address space, even
> > when used in code with 64bit addresses. That's the most useful
> > behaviour for it.
> 
>  So what should "la $2,0x80000000($3)" do when using 64-bit addresses?  
> Replace/supplement the offset with a symbol as suitable...

Hm, looks like we break somebody's assumptions regardless what we do.
So leaving la as it is and warn about its use seems to be best.


Thiemo

  reply	other threads:[~2005-04-15 11:28 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-14 22:08 Eric Christopher
2005-04-14 22:38 ` Thiemo Seufer
2005-04-15 10:32   ` Maciej W. Rozycki
2005-04-15 11:28     ` Thiemo Seufer [this message]
2005-04-15 16:50       ` Eric Christopher
2005-04-15 19:37         ` Thiemo Seufer
2005-04-15 16:50     ` Eric Christopher
2005-04-15 17:03       ` Maciej W. Rozycki
2005-04-15 17:07         ` Eric Christopher
2005-04-18 12:46           ` Maciej W. Rozycki
2005-04-15 17:18         ` Thiemo Seufer
2005-04-15 17:35           ` Paul Koning
2005-04-15 18:56             ` Maciej W. Rozycki
2005-04-15 19:25               ` Paul Koning
2005-04-15 19:28               ` Paul Koning
2005-04-15 19:35                 ` Thiemo Seufer
2005-04-16 10:26                   ` Richard Sandiford
2005-04-15 20:57               ` cgd
2005-04-18 12:58                 ` Maciej W. Rozycki
2005-04-18 19:32                   ` Eric Christopher
2005-04-16 10:31               ` Richard Sandiford

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=20050415112755.GA21496@hattusa.textio \
    --to=ths@networkno.de \
    --cc=binutils@sources.redhat.com \
    --cc=cgd@broadcom.com \
    --cc=erchrist@cisco.com \
    --cc=macro@linux-mips.org \
    --cc=newlib@sources.redhat.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).