From: chenglulu <chenglulu@loongson.cn>
To: Xi Ruoyao <xry111@xry111.site>, gcc-patches@gcc.gnu.org
Cc: i@xen0n.name, xuchenghua@loongson.cn, mengqinggang@loongson.cn
Subject: Re: Pushed: [PATCH v2] LoongArch: Disable explicit reloc for TLS LD/GD with -mexplicit-relocs=auto
Date: Tue, 23 Jan 2024 16:35:37 +0800 [thread overview]
Message-ID: <94836b1e-f9dc-c05e-3d30-4140ceaf8b9a@loongson.cn> (raw)
In-Reply-To: <9195928af9ccbb86380fffdc41aefebc25001a04.camel@xry111.site>
在 2024/1/23 下午4:04, Xi Ruoyao 写道:
> On Tue, 2024-01-23 at 10:37 +0800, chenglulu wrote:
>> LGTM!
>>
>> Thanks!
> Pushed v2 as attached. The only change is in the comment: Qinggang told
> me TLE LE relaxation actually *requires* explicit relocs.
>
>
I think one of the reasons is also because we cannot properly use a
macro to describe TLS LE relaxation.
prev parent reply other threads:[~2024-01-23 8:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 18:42 [PATCH] " Xi Ruoyao
2024-01-23 2:37 ` chenglulu
2024-01-23 8:04 ` Pushed: [PATCH v2] " Xi Ruoyao
2024-01-23 8:35 ` chenglulu [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=94836b1e-f9dc-c05e-3d30-4140ceaf8b9a@loongson.cn \
--to=chenglulu@loongson.cn \
--cc=gcc-patches@gcc.gnu.org \
--cc=i@xen0n.name \
--cc=mengqinggang@loongson.cn \
--cc=xry111@xry111.site \
--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).