← Back to context Comment by krackers 5 hours ago For it to be memory safe, do you have to disable the JIT? 5 comments krackers Reply pizlonator 5 hours ago Yeah amluto 4 hours ago It sounds technically possible to build a JIT where a verifier checks that the JIT-generated code is correctly pizlonated before allowing it to become executable. :) Ohentis 3 hours ago I think it makes more sense to verify that the jit is correct than to verify that it's output is correct at runtime. 1 reply → pizlonator 3 hours ago YesI have a new tech called SaRCAsm, which is a memory-safe assembler. So the next step is a "Sarcastic JIT" :-)
pizlonator 5 hours ago Yeah amluto 4 hours ago It sounds technically possible to build a JIT where a verifier checks that the JIT-generated code is correctly pizlonated before allowing it to become executable. :) Ohentis 3 hours ago I think it makes more sense to verify that the jit is correct than to verify that it's output is correct at runtime. 1 reply → pizlonator 3 hours ago YesI have a new tech called SaRCAsm, which is a memory-safe assembler. So the next step is a "Sarcastic JIT" :-)
amluto 4 hours ago It sounds technically possible to build a JIT where a verifier checks that the JIT-generated code is correctly pizlonated before allowing it to become executable. :) Ohentis 3 hours ago I think it makes more sense to verify that the jit is correct than to verify that it's output is correct at runtime. 1 reply → pizlonator 3 hours ago YesI have a new tech called SaRCAsm, which is a memory-safe assembler. So the next step is a "Sarcastic JIT" :-)
Ohentis 3 hours ago I think it makes more sense to verify that the jit is correct than to verify that it's output is correct at runtime. 1 reply →
pizlonator 3 hours ago YesI have a new tech called SaRCAsm, which is a memory-safe assembler. So the next step is a "Sarcastic JIT" :-)
Yeah
It sounds technically possible to build a JIT where a verifier checks that the JIT-generated code is correctly pizlonated before allowing it to become executable. :)
I think it makes more sense to verify that the jit is correct than to verify that it's output is correct at runtime.
1 reply →
Yes
I have a new tech called SaRCAsm, which is a memory-safe assembler. So the next step is a "Sarcastic JIT" :-)