public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Xi Ruoyao <xry111@xry111.site>
To: mengqinggang <mengqinggang@loongson.cn>, binutils@sourceware.org
Cc: Nick Clifton <nickc@redhat.com>
Subject: Re: [PATCH] LoongArch: Disallow TLS transition when a section contains TLS_IE64 or TLS_DESC64 reloc
Date: Fri, 26 Jan 2024 17:45:01 +0800	[thread overview]
Message-ID: <62281ee2d617316184ba23c6bf729b9b9ba53b6b.camel@xry111.site> (raw)
In-Reply-To: <dbd6e191-0647-a371-9ea7-6bb63160dcba@loongson.cn>

On Fri, 2024-01-26 at 16:40 +0800, mengqinggang wrote:
> We will send a patch to fix this and some other questions today.

Just a note: with e14f7abaf81d5d0aa7898570024286de8c188817 gas is not
emitting R_LARCH_RELAX for 2-operand la.tls.ie:

$ cat t.s
.globl _start
_start:
  la.tls.ie $a0, foo

.section .tdata
foo: .word 114514
$ gas/as-new t.s -o t.o
$ binutils/objdump -dr t.o

t.o:     file format elf64-loongarch


Disassembly of section .text:

0000000000000000 <_start>:
   0:	1a000004 	pcalau12i   	$a0, 0
			0: R_LARCH_TLS_IE_PC_HI20	foo
   4:	28c00084 	ld.d        	$a0, $a0, 0
			4: R_LARCH_TLS_IE_PC_LO12	foo

I guess this needs to be fixed too.


-- 
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University

      reply	other threads:[~2024-01-26  9:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-25 13:36 Xi Ruoyao
2024-01-25 13:49 ` Nick Clifton
2024-01-25 13:52   ` Xi Ruoyao
2024-01-26  1:43 ` mengqinggang
2024-01-26  8:12   ` Xi Ruoyao
2024-01-26  8:19     ` Xi Ruoyao
2024-01-26  8:40       ` mengqinggang
2024-01-26  9:45         ` 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=62281ee2d617316184ba23c6bf729b9b9ba53b6b.camel@xry111.site \
    --to=xry111@xry111.site \
    --cc=binutils@sourceware.org \
    --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).