6 ms·

You're misinformed, I suspect because you are conflating .NET programs being distributed as bytecode with .NET programs being interpreted. It is true that .NET

by gecko 11y ago

You're misinformed, I suspect because you are conflating .NET programs being distributed as bytecode with .NET programs being interpreted. It is true that .NET programs are traditionally distributed as CLR bytecode. This is similar to a .class file or a .pyc file. But the CLR does now, and always has, had a JIT. E.g., the first line or two of https://msdn.microsoft.com/en-us/library/ht8ecch6(v=vs.71).aspx https://msdn.microsoft.com/en-us/library/ht8ecch6(v=vs.71).a... , which is for .NET 1.1, which explicitly states that, even at that time, the bytecode is JITed prior to execution.

masklinn 11y ago
> You're misinformed, I suspect because you are conflating .NET programs being distributed as bytecode with .NET programs being interpreted. No and no. > But the CLR does now, and always has, had a JIT. And Python has had a JIT[0] for as long as the framework has existed. [0] https://en.wikipedia.org/wiki/Psyco https://en.wikipedia.org/wiki/Psyco now replaced by the pypy project
- heinrich5991 11y ago
  Python doesn't have a JIT by default (CPython, the reference implementation). Does the same apply to .NET?
  - pjmlp 11y ago
    .NET as distributed by Microsoft: - JIT and AOT compilation via NGEN up to .NET 4.5.2 - Starting with .NET 4.6, RyuJIT which uses the Visual C++ backend and exposes SIMD support to .NET languages - When targeting Windows 8 and 8.1, AOT compilation to native code in a format called MDIL. Basically requires dynamic linking on device, everything else will be native code already - When targeting Window 10 store applications onwards, AOT compilation to static executables - .NET Compact Framework also always JITs - .NET Micro Framework is the only one that does interpret MSIL Also Microsoft .NET JIT compilers, with the exception of the .NET Micro Framework always jit the code, there is no threshold to trigger it like on most JVMs.
- Locke1689 11y ago
  .NET is JIT'd in its most popular form, the .NET Framework. Python is interpreted in what was its most popular form, but may not be now, CPython. This is using the definition of a JIT as an execution engine which takes in some form of bytecode and, at runtime, emits architecture-specific assembly code to a page, marks that page executable, and changes the IP to that page. If CPython executes in that manner then I'm mistaken about CPython's execution engine and would also consider CPython to be a JIT.

by gecko 11y ago

masklinn 11y ago

> You're misinformed, I suspect because you are conflating .NET programs being distributed as bytecode with .NET programs being interpreted. No and no. > But the CLR does now, and always has, had a JIT. And Python has had a JIT[0] for as long as the framework has existed. [0] https://en.wikipedia.org/wiki/Psyco https://en.wikipedia.org/wiki/Psyco now replaced by the pypy project

heinrich5991 11y ago
Python doesn't have a JIT by default (CPython, the reference implementation). Does the same apply to .NET?
- pjmlp 11y ago
  .NET as distributed by Microsoft: - JIT and AOT compilation via NGEN up to .NET 4.5.2 - Starting with .NET 4.6, RyuJIT which uses the Visual C++ backend and exposes SIMD support to .NET languages - When targeting Windows 8 and 8.1, AOT compilation to native code in a format called MDIL. Basically requires dynamic linking on device, everything else will be native code already - When targeting Window 10 store applications onwards, AOT compilation to static executables - .NET Compact Framework also always JITs - .NET Micro Framework is the only one that does interpret MSIL Also Microsoft .NET JIT compilers, with the exception of the .NET Micro Framework always jit the code, there is no threshold to trigger it like on most JVMs.
Locke1689 11y ago
.NET is JIT'd in its most popular form, the .NET Framework. Python is interpreted in what was its most popular form, but may not be now, CPython. This is using the definition of a JIT as an execution engine which takes in some form of bytecode and, at runtime, emits architecture-specific assembly code to a page, marks that page executable, and changes the IP to that page. If CPython executes in that manner then I'm mistaken about CPython's execution engine and would also consider CPython to be a JIT.