From: ASSI <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Possiblly bug of cygwin1.dll
Date: Sun, 21 Jan 2024 14:30:00 +0100 [thread overview]
Message-ID: <87fryqizl3.fsf@> (raw)
In-Reply-To: <20240121201051.795a4405576a97ab8729e273@nifty.ne.jp> (Takashi Yano via Cygwin's message of "Sun, 21 Jan 2024 20:10:51 +0900")
Takashi Yano via Cygwin writes:
> I found the cause. In pthread.h of cygwin, PTHREAD_ONCE_INIT is defined as:
> #define PTHREAD_ONCE_INIT { PTHREAD_MUTEX_INITIALIZER, 0 }
> however, libstdc++ initializes non-static pthread_once_t using this macro.
https://www.ibm.com/docs/en/aix/7.3?topic=p-pthread-once-init-macro
https://pubs.opengroup.org/onlinepubs/9699919799/functions/pthread_once.html
"The behavior of pthread_once() is undefined if once_control has
automatic storage duration or is not initialized by PTHREAD_ONCE_INIT."
> I cannot find the POSIX statement that only static pthread_once_t can be
> initialized using PTHREAD_ONCE_INIT. If I do not overlook something,
> this is the problem of cygwin side, isn't it?
You can initialize just about anything with PTHREAD_ONCE_INIT, but you
cannot expect the resulting structure to work as intended if there is
more than instance per library / program, so the libstdc++ object should
be a singleton, not automatic.
Still looks like ATWIL to me…
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
next prev parent reply other threads:[~2024-01-21 13:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 13:44 Takashi Yano
2024-01-19 14:28 ` Corinna Vinschen
2024-01-20 4:18 ` Takashi Yano
2024-01-20 5:13 ` Takashi Yano
2024-01-20 9:13 ` ASSI
2024-01-20 12:24 ` Takashi Yano
2024-01-20 12:46 ` ASSI
2024-01-21 11:10 ` Takashi Yano
2024-01-21 13:30 ` ASSI [this message]
2024-01-22 3:30 ` Takashi Yano
2024-01-22 9:25 ` Corinna Vinschen
2024-01-22 9:57 ` Corinna Vinschen
2024-01-22 11:16 ` Takashi Yano
2024-01-22 11:49 ` Corinna Vinschen
2024-01-22 12:41 ` ASSI
2024-01-22 14:54 ` Corinna Vinschen
2024-01-22 11:06 ` Takashi Yano
2024-01-22 11:42 ` Corinna Vinschen
2024-01-23 3:24 ` Kaz Kylheku
2024-01-24 11:55 ` Takashi Yano
2024-01-24 13:05 ` Corinna Vinschen
2024-01-24 13:11 ` Corinna Vinschen
2024-01-24 20:37 ` Kaz Kylheku
2024-01-24 20:08 ` Kaz Kylheku
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=87fryqizl3.fsf@ \
--to=stromeko@nexgo.de \
--cc=cygwin@cygwin.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).