This is the mail archive of the libc-hacker@sources.redhat.com mailing list for the glibc project.

Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Introduce TRY_STATIC_TLS macro, used in FR-V

From: Alexandre Oliva <aoliva at redhat dot com>
To: Ulrich Drepper <drepper at redhat dot com>
Cc: libc-hacker at sources dot redhat dot com, roland at redhat dot com
Date: 09 Feb 2005 09:06:36 -0200
Subject: Re: Introduce TRY_STATIC_TLS macro, used in FR-V
Organization: Red Hat Global Engineering Services Compiler Team
References: <ork6ppa9ev.fsf@livre.redhat.lsd.ic.unicamp.br><ork6pkeno7.fsf@livre.redhat.lsd.ic.unicamp.br><orr7jqrr74.fsf_-_@livre.redhat.lsd.ic.unicamp.br><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}

References:
- Re: Fujitsu FR-V port (linuxthreads and nptl included)
  - From: Alexandre Oliva
- Introduce TRY_STATIC_TLS macro, used in FR-V
  - From: Alexandre Oliva
- Re: Introduce TRY_STATIC_TLS macro, used in FR-V
  - From: Ulrich Drepper

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]