jit? more like pajit because it's a subhuman idea. just compile your fucking code
inb4 retards claiming jit compilation runs software faster than aot compiled apps after """warming up""".
It is really simple. You make a compiler that out competes the JITs and people will use it. They're not using them for fun. The fun JITs were done in the 90s, like for Self. Since then it's mainly about making interpreted shit faster, not replacing compiled languages.
>>106628503There is (1) circumstance where this is true, and that is if the JIT compiler is allowed to use optimised SIMD instructions and the AOT build was done without SIMD for compatibility.Frankly I think all software should be shipped in source form and the installer should compile it as aggressively optimised as possible on the platform.But C++/Rust people enjoy really really slow compilers so it won't be practical if those languages are being used.
at my work we compile each day for 3 hours to test
>>106628491>jit? more like pajit because it's a subhuman idea. just compile your fucking codeHi mr. Retard,Your graph fails to illustrate how a real, 2025 state of the art JIT works. Your graph basically describes an interpreter, not a JIT. Please complete your college degree before posting.
>>106628491templeOS's main feature is jit compilation at the OS level which makes it very convenient and fun. you just suck at computers
OP is so smart. I want to be smart like OP.>>106628657>reddit spacingF*ck off.
>>106628491Good luck with an AOT compiler when your program generates new bytecode on the fly. In certain circumstances JIT can be faster, such as with dynamic languages where you can pass any type to a function but if you only use a single type for it the JIT can optimize it for only that one type. An AOT compiler won't have the information necessary to do this without typing.JIT compiling has it's place but generally if your programming language requires it to run relatively fast then you're using a shit language.
>>106628678>>reddit spacing>F*ck off.
>>106628542Just JIT your C code with C2MIR.
>>106628807just warm it up bro
>>106628491JIT does have a valid use, that is for dynamic types and generics. C++ code is known for producing extreamly bloated binaries due to all the template bloat. With JIT, generics can be included once, and compiled at runtime as needed. Dynamic types also can significantly reduce the complexity and bloat of some types of code.
Ugly but works. Seen emulators that speed up quite dramatically with Jeet enabled.
For my project where I needed sandboxed C plugins I just implemented WASM interpreter in just over 2K SLOC using computed gotos. It's fast enough for my purposes, no JEET needed (JEET = bloat and vulnerabilities).
