4 ms·
Interesting comment in that thread: "It's worth mentioning the function representation change, since it means closures no longer require runtime code generatio
by kristianp 14y ago
Interesting comment in that thread:
"It's worth mentioning the function representation change, since it means closures no longer require runtime code generation (which among other things allows the heap to be marked non-executable on supported systems)."
Anyone know what that means?
- dylanvee 14y agoMarking the heap's region of memory as non-executable improves security. http://en.wikipedia.org/wiki/Executable_space_protection http://en.wikipedia.org/wiki/Executable_space_protection
- kristianp 14y agoSorry, I wasn't clearer, but I have heard of NX. The part I was wondering about was how the function representation changed.
- JulienSchmidt 14y agohttp://en.wikipedia.org/wiki/NX_bit http://en.wikipedia.org/wiki/NX_bit Edit: dylanvee was faster, the NX-bit is the underlying hardware feature
- axw 14y agoThe gory details are here: https://docs.google.com/document/d/1bMwCey-gmqZVTpRax-ESeVuZGmjwbocYs1iHplK-cjo/pub https://docs.google.com/document/d/1bMwCey-gmqZVTpRax-ESeVuZ... TL;DR: functions are now represented as (function pointer, pointer to a context structure), whereas before they were represented as a single function pointer.