From: Xi Ruoyao <xry111@xry111.site>
To: Huacai Chen <chenhuacai@kernel.org>
Cc: gcc-patches@gcc.gnu.org, Lulu Cheng <chenglulu@loongson.cn>,
Wang Xuerui <i@xen0n.name>, Chenghua Xu <xuchenghua@loongson.cn>
Subject: Re: [PATCH] LoongArch: add -mdirect-extern-access option
Date: Fri, 02 Sep 2022 11:31:59 +0800 [thread overview]
Message-ID: <0246589ef3086259636ada74e6b853b9588c7f40.camel@xry111.site> (raw)
In-Reply-To: <CAAhV-H4WLym-mzkHyEHLyZgpkZBM7+L2xDcY3Ytei29C5E7gXw@mail.gmail.com>
On Fri, 2022-09-02 at 11:12 +0800, Huacai Chen wrote:
> On Thu, Sep 1, 2022 at 6:56 PM Xi Ruoyao <xry111@xry111.site> wrote:
> >
> > We'd like to introduce a new codegen option to align with the old
> > "-Wa,-mla-global-with-pcrel" and avoid a performance & size
> > regression
> > building the Linux kernel with new-reloc toolchain. And it should
> > be
> > also useful for building statically linked executables, firmwares
> > (EDK2
> > for example), and other OS kernels.
> >
> > OK for trunk?
> This seems drop your (1)(2)(3) approach and do a similar thing as "a
> new code model" discussed in another thread?
Step (1) is rejected because they've found some issue with copy
relocation impossible to be solved (there is a plan to drop copy
relocation from other architectures as well). This is a modification of
(2): we add -mdirect-extern-access, but without copy relocation it can
only be used by kernel, static executable, etc. so it's not the default.
In kernel we just use KBUILD_CFLAGS_KERNEL += -mdirect-extern-access.
For modules we use GOT until we can get rid of XKPRANGE.
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2022-09-02 3:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 10:54 Xi Ruoyao
2022-09-02 3:12 ` Huacai Chen
2022-09-02 3:31 ` Xi Ruoyao [this message]
2022-09-02 11:30 ` Xi Ruoyao
2022-09-04 0:52 ` Fangrui Song
2022-09-04 2:26 ` Lulu Cheng
2022-09-04 2:51 ` Xi Ruoyao
2022-09-04 3:22 ` Lulu Cheng
2022-09-04 6:35 ` Xi Ruoyao
2022-09-04 7:00 ` Lulu Cheng
2022-09-04 7:38 ` Fangrui Song
2022-09-04 13:29 ` Xi Ruoyao
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=0246589ef3086259636ada74e6b853b9588c7f40.camel@xry111.site \
--to=xry111@xry111.site \
--cc=chenglulu@loongson.cn \
--cc=chenhuacai@kernel.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=i@xen0n.name \
--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).