mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Xi Ruoyao <xry111@xry111.site>
To: Huacai Chen <chenhuacai@kernel.org>, Arnd Bergmann <arnd@arndb.de>
Cc: loongarch@lists.linux.dev, LKML <linux-kernel@vger.kernel.org>,
	WANG Xuerui <kernel@xen0n.name>,
	Youling Tang <tangyouling@loongson.cn>,
	Jinyang He <hejinyang@loongson.cn>
Subject: Re: [PATCH v2 0/4] LoongArch: Support new relocation types
Date: Thu, 28 Jul 2022 22:05:34 +0800	[thread overview]
Message-ID: <b4e9c57b4e863cc105fbf9a8e6bbfc1407ee35ca.camel@xry111.site> (raw)
In-Reply-To: <CAAhV-H5C3LW-xFV-4KsJZHow3av0qeV-sHUSJTUp=hwHGfO1wg@mail.gmail.com>

On Thu, 2022-07-28 at 20:33 +0800, Huacai Chen wrote:
> Hi, Arnd,

/* snip */

> Could you update the cross-compilers here [1] to make this series be
> possible upstream in the 5.20 cycle? Or we can only do that until new
> binutils/gcc be released?

Hi Huacai and Arnd,

The old toolchain will use

    R_LARCH_PUSH_PCREL _GLOBAL_OFFSET_TABLE_
    R_LARCH_PUSH_GPREL symbol
    R_LARCH_ADD

to perform a PC-relative addressing for a GOT entry, and the new
toolchain will use R_LARCH_GOT_PC_{HI20,LO12}.  Both way are supported
by this series.

I've tested the V3 patch (V2 + suggestions from Youling, I'll sent it
later after rewording the third patch) with both my system toolchain (no
new reloc support) and a toolchain built from binutils & gcc master. 
Both of the build works fine.

So a toolchain update seems not immediately required.
-- 
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University

      reply	other threads:[~2022-07-28 14:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-28 11:49 Xi Ruoyao
2022-07-28 11:54 ` [PATCH v2 1/4] LoongArch: Add section of GOT for kernel module Xi Ruoyao
2022-07-28 11:59 ` [PATCH 2/4] LoongArch: Support R_LARCH_SOP_PUSH_GPREL relocation type in " Xi Ruoyao
2022-07-28 12:30   ` Huacai Chen
2022-07-28 12:33     ` Xi Ruoyao
2022-07-28 12:03 ` [PATCH v2 3/4] LoongArch: Stop using undocumented assembler options Xi Ruoyao
2022-07-28 12:25   ` Huacai Chen
2022-07-28 13:10     ` Xi Ruoyao
2022-07-29  2:46       ` Huacai Chen
2022-07-28 12:04 ` [PATCH v2 4/4] LoongArch: Support modules with new relocation types Xi Ruoyao
2022-07-28 12:41   ` Youling Tang
2022-07-28 13:30     ` Xi Ruoyao
2022-07-28 12:33 ` [PATCH v2 0/4] LoongArch: Support " Huacai Chen
2022-07-28 14:05   ` Xi Ruoyao [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=b4e9c57b4e863cc105fbf9a8e6bbfc1407ee35ca.camel@xry111.site \
    --to=xry111@xry111.site \
    --cc=arnd@arndb.de \
    --cc=chenhuacai@kernel.org \
    --cc=hejinyang@loongson.cn \
    --cc=kernel@xen0n.name \
    --cc=linux-kernel@vger.kernel.org \
    --cc=loongarch@lists.linux.dev \
    --cc=tangyouling@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

all inboxes | Powered by JetHome®