mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Jens Gustedt <jens.gustedt@inria.fr>
To: musl@lists.openwall.com
Subject: Re: musl pthread/tls issue.
Date: Wed, 22 Oct 2014 09:27:42 +0200	[thread overview]
Message-ID: <1413962862.4851.166.camel@eris.loria.fr> (raw)
In-Reply-To: <54474F9D.3090306@i-soft.com.cn>

[-- Attachment #1: Type: text/plain, Size: 1158 bytes --]

Am Mittwoch, den 22.10.2014, 14:33 +0800 schrieb 黄建忠:
> And after a quick look, the problem is in pixman-compiler.h, it defined
> TLS related codes and macros according to specific
> implementation(win32/mingw/pthread and so on).
> By default, the TLS codes will be compiled, if it was disabled, there is
> still a pthread fallback use 'pthread_key_create' and other pthread funcs.

Both, the TLS and pthread codes look fishy to me. They define the tls
"variables" as static which restricts any of them to be used from
inside the same TU. This perhaps may mostly be the case, but it is
certainly a desing restriction if not a flaw.

Maybe the code that errors for you does inline certain functions
according to compiler versions, flags etc, and thus creates several
copies of these static variables? Just a wild guess.

Jens


-- 
:: INRIA Nancy Grand Est ::: AlGorille ::: ICube/ICPS :::
:: ::::::::::::::: office Strasbourg : +33 368854536   ::
:: :::::::::::::::::::::: gsm France : +33 651400183   ::
:: ::::::::::::::: gsm international : +49 15737185122 ::
:: http://icube-icps.unistra.fr/index.php/Jens_Gustedt ::




[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2014-10-22  7:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-22  6:33 黄建忠
2014-10-22  7:08 ` Luca Barbato
2014-10-22  7:17   ` 黄建忠
2014-10-22  7:27 ` Jens Gustedt [this message]
2014-10-22  7:45 ` Szabolcs Nagy
2014-10-24  7:35   ` 黄建忠
2014-10-24 11:32     ` Szabolcs Nagy
2014-10-22  7:58 ` Timo Teras

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=1413962862.4851.166.camel@eris.loria.fr \
    --to=jens.gustedt@inria.fr \
    --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).