From: Ian Lance Taylor <ian@airs.com>
To: "Vladimir Stepanenko" <vlads@juniper.net>
Cc: <gcc-help@gcc.gnu.org>
Subject: Re: mips64-elf-as: missing 'li' macro
Date: Sat, 08 Oct 2005 05:06:00 -0000 [thread overview]
Message-ID: <m3irw81ttc.fsf@gossamer.airs.com> (raw)
In-Reply-To: <F07F17B61B7FF545BC7D7E4BFBE15D2A019FD8F8@hadron.jnpr.net>
"Vladimir Stepanenko" <vlads@juniper.net> writes:
> Latest version of mips64-elf-as produces an error message when
> assembling
> li $1, 0xc000000000000000
>
> start.S:154: Error: Number (0xc000000000000000) larger than 32 bits
>
> Previously (in mips64vr5xxx-elf-as version 2.9-gnupro-99r1) this macro
> was expanded as
> lui $1, 0xc000
> dsll32 $1, $1, 0x10
>
> Does any particular mips64 architecture support this macro extension or
> 64-bit immediates are not allowed at all?
This question is about the assembler, and would be better directed to
binutils@sourceware.org. See http://sourceware.org/binutils/.
I believe the answer is to use 'dli' if you want to load a 64-bit
constant. Note that your 2.9-gnupro-99r1 toolchain is six years old.
Ian
prev parent reply other threads:[~2005-10-08 5:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-08 4:46 Vladimir Stepanenko
2005-10-08 5:06 ` Ian Lance Taylor [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=m3irw81ttc.fsf@gossamer.airs.com \
--to=ian@airs.com \
--cc=gcc-help@gcc.gnu.org \
--cc=vlads@juniper.net \
/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).