From: Fangrui Song <i@maskray.me>
To: musl@lists.openwall.com, Tatsuyuki Ishi <ishitatsuyuki@gmail.com>
Subject: Re: [musl] Draft riscv64 TLSDESC implementation
Date: Sun, 21 Jan 2024 15:48:55 -0800 [thread overview]
Message-ID: <DS7PR12MB57650AE34ABCCB41BA6123A3CB762@DS7PR12MB5765.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20240121222831.GC4163@brightrain.aerifal.cx>
On Sun, Jan 21, 2024 at 2:28 PM Rich Felker <dalias@libc.org> wrote:
>
> On Tue, Aug 22, 2023 at 01:38:21PM -0400, Rich Felker wrote:
> > The psABI work is not finalized, but based on the current status of
> > https://github.com/riscv-non-isa/riscv-elf-psabi-doc/pull/373, I think
> > the attached is a valid (but untested) implementation of TLSDESC for
> > riscv64. Actually activating it requires also adding the relocation
> > type macro to riscv64/reloc.h.
> >
> > If any rv folks could look it over and make sure I haven't made any
> > stupid asm errors or missed any obvious optimizations, that would help
> > to quickly get this merged when the psABI is finalized.
> >
> > Rich
>
> > .text
> > .global __tlsdesc_static
> > .hidden __tlsdesc_static
> > .type __tlsdesc_static,%function
> > __tlsdesc_static:
> > ld a0,8(a0)
> > jr t0
> >
> > .global __tlsdesc_dynamic
> > .hidden __tlsdesc_dynamic
> > .type __tlsdesc_dynamic,%function
> > __tlsdesc_dynamic:
> > add sp,sp,-8
> > sd t1,(sp)
> > sd t2,8(sp)
> >
> > ld t2,-8(tp) # t2=dtv
> >
> > ld a0,8(a0) # a0=&{modidx,off}
> > ld t1,8(a0) # t1=off
> > ld a0,(a0) # a0=modidx
> > sll a0,a0,3 # a0=8*modidx
> >
> > add a0,a0,t2 # a0=dtv+8*modidx
> > ld a0,(a0) # a0=dtv[modidx]
> > add a0,a0,t1 # a0=dtv[modidx]+off
> > sub a0,a0,tp # a0=dtv[modidx]+off-tp
> >
> > ld t1,(sp)
> > ld t2,8(sp)
> > add sp,sp,8
> > jr t0
>
> Any feedback on this? Offhand, it looks like adjusting sp by 8 is
> wrong and that should be 16. Anything else? Does anyone have recent
> enough tooling to test this?
Tatsuyuki, do you have links to the latest version of
gcc/binutils/glibc patches?
Downloading patches from these mailing lists is probably a large
hurdle for many users, so having the relevant repositories online may
help.
mold has implemented RISC-V TLSDESC.
On the LLVM side, I have reviewed
https://github.com/llvm/llvm-project/pull/66915 and am waiting for it
to land, before I can check the lld status.
next prev parent reply other threads:[~2024-01-21 23:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 17:38 Rich Felker
2024-01-21 22:28 ` Rich Felker
2024-01-21 23:48 ` Fangrui Song [this message]
2024-01-22 0:03 ` Rich Felker
2024-01-22 3:41 ` Tatsuyuki Ishi
2024-01-23 8:52 ` Fangrui Song
2024-01-23 13:26 ` Rich Felker
2024-01-25 6:48 ` Fangrui Song
[not found] ` <CAN30aBFHo2NmDknvhVUyWOvXuhvFZBvrzO6vm1PqEB7e2P9NTg@mail.gmail.com>
2024-01-27 0:11 ` Fangrui Song
[not found] ` <DS7PR12MB576582CD9FF325AAE6FA8B0CCB762@DS7PR12MB5765.namprd12.prod.outlook.com>
2024-01-22 3:38 ` Tatsuyuki Ishi
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=DS7PR12MB57650AE34ABCCB41BA6123A3CB762@DS7PR12MB5765.namprd12.prod.outlook.com \
--to=i@maskray.me \
--cc=ishitatsuyuki@gmail.com \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).