From: Alexandre Oliva <aoliva@redhat.com>
To: Ulrich Drepper <drepper@redhat.com>
Cc: libc-hacker@sources.redhat.com, roland@redhat.com
Subject: Re: Introduce TRY_STATIC_TLS macro, used in FR-V
Date: Wed, 09 Feb 2005 11:07:00 -0000 [thread overview]
Message-ID: <or6512ro03.fsf@livre.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: <4209E170.6010705@redhat.com>
On Feb 9, 2005, Ulrich Drepper <drepper@redhat.com> wrote:
> No. No changes like this to generic code. There is no need whatsoever.
> If some moron "designed" TLS on an arch incorrectly, add an
> _dl_catch_error block to catch the _dl_signal_error call and handle it.
Just because another moron couldn't think of a better way to design
it? How stupid is this going to get?
--
Alexandre Oliva http://www.ic.unicamp.br/~oliva/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}
next prev parent reply other threads:[~2005-02-09 11:07 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ork6ppa9ev.fsf@livre.redhat.lsd.ic.unicamp.br>
2005-02-07 9:15 ` Fujitsu FR-V port (linuxthreads and nptl included) Alexandre Oliva
2005-02-07 19:37 ` Roland McGrath
2005-02-09 9:38 ` elf.h changes for FR-V FDPIC and TLS Alexandre Oliva
2005-03-13 9:17 ` Roland McGrath
2005-02-09 9:48 ` Fujitsu FR-V port (linuxthreads and nptl included) Alexandre Oliva
2005-02-09 9:57 ` Ulrich Drepper
2005-02-09 11:30 ` Alexandre Oliva
2005-03-13 9:15 ` Roland McGrath
2005-02-09 9:57 ` Introduce TRY_STATIC_TLS macro, used in FR-V Alexandre Oliva
2005-02-09 10:10 ` Ulrich Drepper
2005-02-09 11:07 ` Alexandre Oliva [this message]
2005-02-09 10:08 ` FR-V TLS macros Alexandre Oliva
2005-02-09 10:13 ` Ulrich Drepper
2005-02-09 11:15 ` Alexandre Oliva
2005-03-13 9:09 ` Roland McGrath
2005-02-09 11:01 ` FR-V PLT audit Alexandre Oliva
2005-02-09 11:15 ` Ulrich Drepper
2005-02-10 5:16 ` Richard Henderson
2005-02-10 6:43 ` Roland McGrath
2005-02-10 7:06 ` Richard Henderson
2005-02-10 7:19 ` Roland McGrath
2005-02-10 7:51 ` Richard Henderson
2005-02-10 9:03 ` Roland McGrath
2005-02-10 16:51 ` Richard Henderson
2005-02-09 11:02 ` FR-V set_tid_address syscall number Alexandre Oliva
2005-02-09 11:11 ` Ulrich Drepper
2005-02-09 11:36 ` Alexandre Oliva
2005-02-09 11:02 ` using pre-TCB padding for static TLS Alexandre Oliva
2005-02-09 11:14 ` Ulrich Drepper
2005-02-09 11:35 ` Alexandre Oliva
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=or6512ro03.fsf@livre.redhat.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=drepper@redhat.com \
--cc=libc-hacker@sources.redhat.com \
--cc=roland@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).