These are chat archives for Microsoft/visualfsharp

29th
Jul 2015
Steffen Forkmann
@forki
Jul 29 2015 07:42
"F# developers are encouraged to wait to deploy the .NET Framework 4.6." - http://blogs.msdn.com/b/dotnet/archive/2015/07/28/ryujit-bug-advisory-in-the-net-framework-4-6.aspx#recommendation
Dave Thomas
@7sharp9
Jul 29 2015 08:47
The data suggests that the vast majority of .NET developers will not experience this same issue
Hmm
Steffen Forkmann
@forki
Jul 29 2015 08:57
See the good thing is that F# is not installed by default.
Raymen Scholten
@raymens
Jul 29 2015 08:58
They expected the bug and thus didn't install F# by default :trollface:
Steffen Forkmann
@forki
Jul 29 2015 08:59
The thing is: there are already 3 critical ryujit issues. 2 in C#
They still recommend to keep it enabled
dotnet/coreclr#1299
It gives wrong results in production. No exception, just wrong results.
Raymen Scholten
@raymens
Jul 29 2015 09:05
how would that issue look if there were no nulls :)
But on a more serious note, IMO they should disable RyuJit for the time being on production systems
Isaac Abraham
@isaacabraham
Jul 29 2015 09:36
i would be very, very surprised to see that happen
Steffen Forkmann
@forki
Jul 29 2015 09:56
why?
Isaac Abraham
@isaacabraham
Jul 29 2015 09:56
read the blog post
Steffen Forkmann
@forki
Jul 29 2015 09:57
yes. it's trying to make things look harmless, but IMHO that's only making things worse
Isaac Abraham
@isaacabraham
Jul 29 2015 10:18
hey, there are no exceptions. so it surely can't be that bad.
exceptions = bad. results = good.
Steffen Forkmann
@forki
Jul 29 2015 10:30
Lol
Steffen Forkmann
@forki
Jul 29 2015 11:42
Is there a way to run the F# unit tests (including property based tests) against ryujit?
If I use a fresh machine with win10 + VS2015. Would it use ryujit for the tests?
Raymen Scholten
@raymens
Jul 29 2015 12:15
Doesn't all .NET stuff use RyuJit on W10 or any .NET 4.6 installation?
Steffen Forkmann
@forki
Jul 29 2015 12:16
yeah, but I don't know if the tests run in debug mode or something like that
Steffen Forkmann
@forki
Jul 29 2015 14:11
OK I have VS2015, VS2015 SDK and WIn10. the build fails.
blob
this unrelated to jit, but what is it
Tony Williams
@TWith2Sugars
Jul 29 2015 18:54
well: Microsoft/visualfsharp#536
dotnet/coreclr#1302
Lincoln Atkinson
@latkin
Jul 29 2015 21:17
RyuJIT is only for x64
processes running at 32-bit do not use RyuJIT
64-bit procs will use it by default if you have .NET 4.6 installed. You can disable it with reg keys.
Lincoln Atkinson
@latkin
Jul 29 2015 21:22
some of the compiler tests do run as x64, but not very many by default I beleive
from the compiler's perspective, marking an assembly as x86/anycpu/x64 is just setting a couple of bytes in the PE header - it's not something that's particularly "interesting" so we don't do extensive validation of runtime behavior there
Steffen Forkmann
@forki
Jul 29 2015 21:31
Yeah I understand. And we always trusted the jitter. I'm just interested if we would already have spotted one of the 3 errors with our test suite.
Lincoln Atkinson
@latkin
Jul 29 2015 21:32
probably would have found something - actually it wouldn't be a bad idea to tweak RunAll.pl to stick --platform:x64 on every test and just see what happens