From: Paul Koning <pkoning@equallogic.com>
To: ths@networkno.de
Cc: macro@linux-mips.org, echristo@redhat.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 17:35:00 -0000 [thread overview]
Message-ID: <16991.64361.508338.807589@gargle.gargle.HOWL> (raw)
In-Reply-To: <20050415171813.GG21496@hattusa.textio>
>>>>> "Thiemo" == Thiemo Seufer <ths@networkno.de> writes:
>> Of course it is zero-extended. Otherwise it would be a different
>> one; actually in the CKSEG0 space rather than XKUSEG. If you want
>> the former, what's wrong with 0xffffffff80000000? -- please keep
>> in mind we are talking about 64-bit addressing.
Thiemo> But people used to use "la $2, 0x80000000" in order to get a
Thiemo> sign-extended address. Loading two different addresses with
Thiemo> the same code is at least surprising. I see la in 64bit mode
Thiemo> as backward compatibility legacy, and this suggests not to
Thiemo> change its behaviour.
Agreed. Addresses are signed values on MIPS. Dxx opcodes are 64 bit
operations; xx opcodes (when Dxx also exists) are 32 bit operations.
So DLI loads a 64 bit int and LI a 32 bit int. DLA loads a 64 bit
address and LA a 32 bit address. So the operand of LA should be a
construct that is a valid 32 bit address (and 0x80000000 is one such)
and it should be expanded into instructions that produce a valid
representation of that address in a register (i.e., with sign
extension if the registers are 64 bits).
paul
next prev parent reply other threads:[~2005-04-15 17:35 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
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 [this message]
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=16991.64361.508338.807589@gargle.gargle.HOWL \
--to=pkoning@equallogic.com \
--cc=binutils@sources.redhat.com \
--cc=cgd@broadcom.com \
--cc=echristo@redhat.com \
--cc=macro@linux-mips.org \
--cc=newlib@sources.redhat.com \
--cc=ths@networkno.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).