public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Latest perl JSON::XS failing when threaded
Date: Sun, 13 Mar 2016 17:21:00 -0000	[thread overview]
Message-ID: <87ziu2e1kv.fsf@Rainer.invalid> (raw)
In-Reply-To: <CAHSx_SvqC+ajoCQ01S+j8wrwqG0B=m0mK5O+o4PQyS-THBWSYQ@mail.gmail.com>	(Wayne Davison's message of "Thu, 3 Mar 2016 15:54:29 -0800")

Wayne Davison writes:
> I updated cygwin today, and now perl JSON::XS fails to be able to
> decode json data if it is run in a multi-threaded script.

As said before, the use of JSON::XS with threads is not supported by
upstream.  That said, I've found a patch at least for the scenario that
your test case uses.  Some situations would have degraded performance,
however, although these have seemingly not been supported in earlier
versions of JSON::XS, so no regressions in existing code are expected to
occur.


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

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  parent reply	other threads:[~2016-03-13 17:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-03 23:54 Wayne Davison
2016-03-04  8:53 ` Achim Gratz
2016-03-04 19:19   ` Achim Gratz
2016-03-05 17:51 ` Achim Gratz
2016-03-13 17:21 ` Achim Gratz [this message]
2016-03-15 22:20   ` Wayne Davison
2016-06-17 20:29     ` Achim Gratz

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=87ziu2e1kv.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).