From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: gcc and 128-bit compare/exchange
Date: Wed, 11 Mar 2020 18:31:26 +0100 [thread overview]
Message-ID: <87imjalrwx.fsf@Rainer.invalid> (raw)
In-Reply-To: <0fc8a150-99b1-34dc-0dfb-a096fc3b2096@cs.umass.edu> (Eliot Moss's message of "Wed, 11 Mar 2020 02:13:40 -0400")
Eliot Moss writes:
> What I am really reporting is that Cygwin is giving the pthread mutex form
> when it should not be. My CPU clearly has the capability, and the compiler clearly
> knows how to emit the instruction, since the __sync form does it. What is
> mysterious and tangled is why libatomic / libc are not delivering the desired
> version of the atomic compare-exchange function.
Assuming you want to use a library, it would have to detect this
capability at runtime (unless you force-build for a single CPU
architecture) and dispatch different code based on the result. It's
probably the latter part that's missing on Cygwin.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
prev parent reply other threads:[~2020-03-11 17:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 2:29 Eliot Moss
2020-03-09 2:59 ` Eliot Moss
2020-03-10 20:35 ` Brian Inglis
2020-03-10 21:13 ` Eliot Moss
2020-03-11 5:31 ` Brian Inglis
2020-03-11 6:13 ` Eliot Moss
2020-03-11 16:30 ` Brian Inglis
2020-03-12 3:36 ` Eliot Moss
2020-03-12 21:13 ` Brian Inglis
2020-03-12 22:49 ` Eliot Moss
2020-03-13 5:35 ` Brian Inglis
2020-03-11 17:31 ` Achim Gratz [this message]
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=87imjalrwx.fsf@Rainer.invalid \
--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).