News for hackers. Stuff that matters.
Re:A Race of Two Compilers: GraalVM JIT versus HotSpot JIT C... by chrisseaton on Sunday June 16, 2019 @10:46AM (#20195702)
Some people differentiate between just-in-time compilation, which is what for example .NET does (or did, last time I checked), where it just literally compiles it as it would ahead-of-time, but at the last second before executing it for the first time, and dynamic compilation, which is for example what Graal does - compiling based on runtime conditions, possibly multiple times with different results as the program executes.
Re:A Race of Two Compilers: GraalVM JIT versus HotSpot JIT C... by lewurm on Sunday June 16, 2019 @05:22PM (#20197968)
> [...] which is what for example .NET does.

.NET is the platform. There are different implementations for it doing different things.

JIT compilation is still different to AOT even without profile guided optimizations. Simple example: In AOT code you can't embed pointers easily and is often solved with indirection (e.g. something like GOT in ELF).

Re:A Race of Two Compilers: GraalVM JIT versus HotSpot JIT C... by chrisseaton on Sunday June 16, 2019 @06:35PM (#20198402)
> There are different implementations for it doing different things.

And are they now speculative? They weren't for the first 15 years or so.

Re:A Race of Two Compilers: GraalVM JIT versus HotSpot JIT C... by lewurm on Monday June 17, 2019 @04:31AM (#20200976)
CoreCLR started to implemented Tiered Compilation https://github.com/dotnet/coreclr/blob/master/Documentation/...

It's experimental currently, no profile guided optimizations _yet_

Re:A Race of Two Compilers: GraalVM JIT versus HotSpot JIT C... by pjmlp on Monday June 17, 2019 @09:04AM (#20202481)
.NET Framework supports PGO since .NET 4.5.