[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: libpthread linking problem -- [address@hidden: Re: imagemagick: conv
|
From: |
Neal H. Walfield |
|
Subject: |
Re: libpthread linking problem -- [address@hidden: Re: imagemagick: convert hangs on hurd-i386] |
|
Date: |
Sun, 28 Jan 2007 23:32:14 +0100 |
|
User-agent: |
Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.6 (Maruoka) FLIM/1.14.6 (Marutamachi) APEL/10.6 Emacs/21.4 (i386-pc-linux-gnu) MULE/5.0 (SAKAKI) |
At Sat, 27 Jan 2007 00:21:15 +0100,
Samuel Thibault wrote:
> > And why do we need all three of `__NAME', `_NAME' and `NAME'?
>
> __NAME is usually used for letting libpthread be sure to call its own
> functions, while NAME can be overriden by other libraries. I don't know
> for _NAME.
NAME is a static inline which checks if the current invocation takes
the critical path and either performs the critical path functionality
inline or calls _NAME for the non-critical path functionality.
Because it may not be inlined, NAME is also provided as a normal
symbol.
This optimization was in Mark's original code. I just retained it.
Neal