public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Xi Ruoyao <xry111@xry111.site>
To: liuzhensong <liuzhensong@loongson.cn>, binutils@sourceware.org
Cc: i.swmail@xen0n.name, maskray@google.com, xuchenghua@loongson.cn,
	 mengqinggang@loongson.cn, huangpei@loongson.cn,
	chenglulu@loongson.cn,  caiyinyu@loongson.cn
Subject: Re: [PATCH v2 2/6] LoongArch:opcodes: Add new reloc types.
Date: Thu, 21 Jul 2022 15:51:50 +0800	[thread overview]
Message-ID: <59572c7c8856cb3e7b65c281a5b05f250712af67.camel@xry111.site> (raw)
In-Reply-To: <ca165756-e2c2-00f6-0737-0158e389266e@loongson.cn>

On Thu, 2022-07-21 at 14:02 +0800, liuzhensong wrote:

> 
> It seems default for addi.d/ld.d to access extreme address.
> Simple example of abs32:
> address range of abs32 :  0~0xffffffff
> sym address: 0xfffff800
> lui12.w $rd, 0xfffff
> ori $rd, $d, 0x800
> $rd is 0xfffff800
> Obviously, lu12i.w and addi.w/ld.w can not get address > 0xfffff7fc

Hmm... Wouldn't "addi.{w/d} $t0, $zero, -0x800" work for this?


-- 
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University

  reply	other threads:[~2022-07-21  7:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-21  1:37 [PATCH v2 0/6] Add new relocations for LoongArch liuzhensong
2022-07-21  1:37 ` [PATCH v2 1/6] bfd: Add supported for LoongArch new relocations liuzhensong
2022-07-21  1:37 ` [PATCH v2 2/6] LoongArch:opcodes: Add new reloc types liuzhensong
2022-07-21  2:30   ` Xi Ruoyao
2022-07-21  6:02     ` liuzhensong
2022-07-21  7:51       ` Xi Ruoyao [this message]
2022-07-21  8:26         ` liuzhensong
2022-07-21  1:37 ` [PATCH v2 3/6] LoongArch: gas: " liuzhensong
2022-07-21  1:37 ` [PATCH v2 4/6] LoongArch: Move ifunc info to rela.dyn from rela.plt liuzhensong
2022-07-21  1:37 ` [PATCH v2 5/6] bfd: Delete R_LARCH_NONE from dyn info of LoongArch liuzhensong

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=59572c7c8856cb3e7b65c281a5b05f250712af67.camel@xry111.site \
    --to=xry111@xry111.site \
    --cc=binutils@sourceware.org \
    --cc=caiyinyu@loongson.cn \
    --cc=chenglulu@loongson.cn \
    --cc=huangpei@loongson.cn \
    --cc=i.swmail@xen0n.name \
    --cc=liuzhensong@loongson.cn \
    --cc=maskray@google.com \
    --cc=mengqinggang@loongson.cn \
    --cc=xuchenghua@loongson.cn \
    /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).