Re: [Gc] Linux emulation on Windows 10

--===============1304085946==
Content-Type: multipart/alternative; boundary=001a11c171beffdecd05491f61db

--001a11c171beffdecd05491f61db
Content-Type: text/plain; charset=UTF-8

My understanding is that updates to the Windows Subsystem for Linux are
essentially not being merged to the mainline release branch updates Windows
users normally receive, and there have been many bugs that have been
resolved over the last several months that are only available via Insider
builds. If your user really wants to use that environment seriously (while
understanding it's still a beta), I'd suggest to them they need to update
to the Fast ring of Insider builds (and accept the risks involved).

On Wed, Feb 22, 2017 at 5:51 AM, Florian Weimer <[email protected]> wrote:

> * Ivan Maidanski:
>
> > Pthread_cond_wait is used only by parallel marker inside GC. So it
> > seems the right guess. I don't have a workaround suggestion though
> > (except for the mentioned one).
>
> If the futex usage by the condvar is problematic, maybe the new
> condvar algorithm in glibc 2.25 will fix it by accident?
>
> I test glibc sporadically with the subsystem, but with the current
> (non-insider) build at least, there is so much breakage in the glibc
> test suite that the results are pretty much meaningless.
>
> In addition, I suspect that some antivirus software breaks the
> subsystem when it is used to build new binaries.
> _______________________________________________
> bdwgc mailing list
> [email protected]
> https://lists.opendylan.org/mailman/listinfo/bdwgc
>

--001a11c171beffdecd05491f61db
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">My understanding is that updates to the Windows Subsystem =
for Linux are essentially not being merged to the mainline release branch u=
pdates Windows users normally receive, and there have been many bugs that h=
ave been resolved over the last several months that are only available via =
Insider builds. If your user really wants to use that environment seriously=
 (while understanding it&#39;s still a beta), I&#39;d suggest to them they =
need to update to the Fast ring of Insider builds (and accept the risks inv=
olved).=C2=A0</div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote=
">On Wed, Feb 22, 2017 at 5:51 AM, Florian Weimer <span dir=3D"ltr">&lt;<a =
href=3D"mailto:[email protected]" target=3D"_blank">[email protected]</a>&gt;=
</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex">* Ivan Maidanski:<br>
<br>
&gt; Pthread_cond_wait is used only by parallel marker inside GC. So it<br>
&gt; seems the right guess. I don&#39;t have a workaround suggestion though=
<br>
&gt; (except for the mentioned one).<br>
<br>
If the futex usage by the condvar is problematic, maybe the new<br>
condvar algorithm in glibc 2.25 will fix it by accident?<br>
<br>
I test glibc sporadically with the subsystem, but with the current<br>
(non-insider) build at least, there is so much breakage in the glibc<br>
test suite that the results are pretty much meaningless.<br>
<br>
In addition, I suspect that some antivirus software breaks the<br>
subsystem when it is used to build new binaries.<br>
<div class=3D"HOEnZb"><div class=3D"h5">______________________________<wbr>=
_________________<br>
bdwgc mailing list<br>
<a href=3D"mailto:[email protected]">[email protected]</a><=
br>
<a href=3D"https://lists.opendylan.org/mailman/listinfo/bdwgc" rel=3D"noref=
errer" target=3D"_blank">https://lists.opendylan.org/<wbr>mailman/listinfo/=
bdwgc</a><br>
</div></div></blockquote></div><br></div>

--001a11c171beffdecd05491f61db--

--===============1304085946==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
bdwgc mailing list
[email protected]
https://lists.opendylan.org/mailman/listinfo/bdwgc
--===============1304085946==--