public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: libc-alpha@sourceware.org,  joseph@codesourcery.com
Subject: Re: [PATCH v7 07/17] RISC-V: Thread-Local Storage Support
Date: Wed, 11 Jul 2018 15:28:00 -0000	[thread overview]
Message-ID: <mvmy3eh4ws5.fsf@suse.de> (raw)
In-Reply-To: <20180127035744.10058-8-palmer@dabbelt.com> (Palmer Dabbelt's message of "Fri, 26 Jan 2018 19:57:34 -0800")

On Jan 26 2018, Palmer Dabbelt <palmer@dabbelt.com> wrote:

> +/* Magic for libthread_db to know how to do THREAD_SELF.  */
> +# define DB_THREAD_SELF \
> +  CONST_THREAD_AREA (32, TLS_TCB_OFFSET + TLS_PRE_TCB_SIZE)

Why CONST_THREAD_AREA?  Shouldn't that use REGISTER?

Andreas.

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."

  reply	other threads:[~2018-07-11 15:28 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-27  3:58 RISC-V glibc port, v7 Palmer Dabbelt
2018-01-27  3:58 ` [PATCH v7 05/17] RISC-V: ABI Implementation Palmer Dabbelt
2018-01-29 16:35   ` Joseph Myers
2018-01-29 16:39     ` Palmer Dabbelt
2018-01-27  3:58 ` [PATCH v7 02/17] Skeleton documentation for the RISC-V port Palmer Dabbelt
2018-02-05  9:19   ` Andreas Schwab
2018-02-08 21:13     ` Palmer Dabbelt
2018-02-08 21:33       ` Jim Wilson
2018-02-12 10:09         ` Andreas Schwab
2018-01-27  3:58 ` [PATCH v7 03/17] Add RISC-V entries to config.h.in Palmer Dabbelt
2018-01-27  8:08 ` [PATCH v7 16/17] Add RISC-V to build-many-glibcs.py Palmer Dabbelt
2018-01-27  8:12 ` [PATCH v7 09/17] RISC-V: Hard Float Support Palmer Dabbelt
2018-01-27  8:13 ` [PATCH v7 17/17] RISC-V: Add ipc_priv.h Palmer Dabbelt
2018-01-27  8:40 ` [PATCH v7 07/17] RISC-V: Thread-Local Storage Support Palmer Dabbelt
2018-07-11 15:28   ` Andreas Schwab [this message]
2018-01-27  8:59 ` [PATCH v7 04/17] Add documentation for __riscv_flush_icache Palmer Dabbelt
2018-01-27  9:04 ` [PATCH v7 13/17] RISC-V: Linux Startup and Dynamic Loading Code Palmer Dabbelt
2018-01-27  9:05 ` [PATCH v7 15/17] RISC-V: Build Infastructure Palmer Dabbelt
2018-01-27  9:07 ` [PATCH v7 01/17] sysdeps/init_array: Add PREINIT_FUNCTION to crti.S Palmer Dabbelt
2018-01-27  9:20 ` [PATCH v7 06/17] RISC-V: Startup and Dynamic Loading Code Palmer Dabbelt
2018-01-29 16:36   ` Joseph Myers
2018-01-29 16:56     ` Palmer Dabbelt
2018-01-27 12:12 ` [PATCH v7 08/17] RISC-V: Generic <math.h> and soft-fp Routines Palmer Dabbelt
2018-01-27 12:19 ` [PATCH v7 14/17] RISC-V: Add ABI Lists Palmer Dabbelt
2018-01-27 12:34 ` [PATCH v7 11/17] RISC-V: Linux Syscall Interface Palmer Dabbelt
2018-01-27 12:34 ` [PATCH v7 10/17] RISC-V: Atomic and Locking Routines Palmer Dabbelt
2018-01-27 15:07 ` [PATCH v7 12/17] RISC-V: Linux ABI Palmer Dabbelt
2018-01-27 21:28 ` RISC-V glibc port, v7 Darius Rad
2018-01-29 16:43 ` Joseph Myers
2018-01-29 22:01   ` Palmer Dabbelt
2018-01-29 22:01     ` Andrew Waterman
2018-01-29 22:09       ` Joseph Myers
2018-01-29 22:09         ` Andrew Waterman
2018-01-29 22:01 ` Palmer Dabbelt

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=mvmy3eh4ws5.fsf@suse.de \
    --to=schwab@suse.de \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.org \
    --cc=palmer@dabbelt.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).