From: Xi Ruoyao <xry111@xry111.site>
To: mengqinggang <mengqinggang@loongson.cn>, binutils@sourceware.org
Cc: Nick Clifton <nickc@redhat.com>, WANG Xuerui <git@xen0n.name>
Subject: Re: [PATCH] gas/NEWS, ld/NEWS: Announce LoongArch changes in 2.42
Date: Tue, 23 Jan 2024 16:35:12 +0800 [thread overview]
Message-ID: <8f6f8d7053f439b40e11ec44ff5a445af36c12c8.camel@xry111.site> (raw)
In-Reply-To: <4fb0b073-693b-521b-6060-f800dfe68403@loongson.cn>
On Tue, 2024-01-23 at 11:56 +0800, mengqinggang wrote:
> > +* TLS LE relaxation is now supported on LoongArch. New relocation
> > + operators %le_hi20_r, %le_lo12r, and %le_add_r are now available, with
> > + la.tls.le now making use of them.
>
>
> la.tls.le still expands to the old instruction sequences. Gcc generates
> new TLS LE
> instruction sequences when -mexplicit-relocs=[always,auto].
Indeed, I'll remove the last sentence.
> > +* Add support for encoding three-expression .align directives on LoongArch
> > + with R_LARCH_ALIGN.
>
>
> R_LARCH_ALIGN only supports the first and the third expressions of .align.
Hmm, using something like .align 16,,4 now triggers a warning, so I'll
remove this paragraph and rather not announce this change to users now.
In the next release we may turn the warning off by default or support
the second expression (?).
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2024-01-23 8:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 19:14 Xi Ruoyao
2024-01-23 3:56 ` mengqinggang
2024-01-23 8:35 ` Xi Ruoyao [this message]
2024-01-23 11:08 ` Nick Clifton
2024-01-23 11:12 ` [PATCH v2] " Xi Ruoyao
2024-01-23 11:28 ` Nick Clifton
2024-01-23 12:38 ` Xi Ruoyao
2024-01-23 16:01 ` Nick Clifton
2024-01-24 3:24 ` [PATCH] " mengqinggang
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=8f6f8d7053f439b40e11ec44ff5a445af36c12c8.camel@xry111.site \
--to=xry111@xry111.site \
--cc=binutils@sourceware.org \
--cc=git@xen0n.name \
--cc=mengqinggang@loongson.cn \
--cc=nickc@redhat.com \
/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).