From: Lulu Cai <cailulu@loongson.cn>
To: Nick Clifton <nickc@redhat.com>
Cc: Xi Ruoyao <xry111@xry111.site>,
mengqinggang <mengqinggang@loongson.cn>,
binutils@sourceware.org
Subject: Re: [PATCH] LoongArch: Fix a bug of getting relocation type
Date: Sat, 27 Jan 2024 21:37:04 +0800 [thread overview]
Message-ID: <e7788dae-8b3e-176f-77c0-0affaba18b3d@loongson.cn> (raw)
In-Reply-To: <0e9da3c59573e61105e26edd35fb9dca095e5d07.camel@xry111.site>
On 1/26/24 7:02 PM, Xi Ruoyao wrote:
> On Fri, 2024-01-26 at 10:55 +0000, Nick Clifton wrote:
>> Hi mengqinggang,
>>
>>> This patch and
>>>
>>> 969f5c0e1 LoongArch: gas: Add support for s9 register
>>> a0aa6f4ab LoongArch: ld: Add support for TLS LE symbol with addend
>>>
>>> need to apply to 2.42 branch.
>> Applied.
>>
>> I am hoping that this is the last of these as I am planning on creating the
>> release on Monday, and I am always worried that last minute changes will
>> bring in new bugs rather than fix old ones...
> Pity that we still have the __thread vs. -mcmodel=extreme issue
> (https://sourceware.org/pipermail/binutils/2024-January/132120.html and
> all the following discussion) not resolved yet.
>
> Possible to apply my straightforward (stupid) "fix" for 2.42 if a proper
> fix cannot be made soon?
>
Hi,
We have sent a new patch to fix the incorrect type transition problem
caused by -mcmodel=extreme.
Now only TLS type transition will be performed for normal.
[PATCH 1/2] LoongArch: Fix incorrect type transition under extreme cmodel
[PATCH 2/2] LoongArch: update test cases about TLS
Can you help us merge it into the 2.42 branch?
Thanks.
Related discussions:
[PATCH] LoongArch: Disallow TLS transition when a section contains
TLS_IE64 or TLS_DESC64 reloc
next prev parent reply other threads:[~2024-01-27 13:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 3:39 mengqinggang
2024-01-26 9:01 ` mengqinggang
2024-01-26 10:55 ` Nick Clifton
2024-01-26 11:02 ` Xi Ruoyao
2024-01-26 11:41 ` Nick Clifton
2024-01-27 13:37 ` Lulu Cai [this message]
2024-01-28 4:14 ` lulu Tsai
2024-01-29 11:24 ` Nick Clifton
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=e7788dae-8b3e-176f-77c0-0affaba18b3d@loongson.cn \
--to=cailulu@loongson.cn \
--cc=binutils@sourceware.org \
--cc=mengqinggang@loongson.cn \
--cc=nickc@redhat.com \
--cc=xry111@xry111.site \
/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).