News for hackers. Stuff that matters.
Re:Go 1.1 RC1 is out by kristianp on Wednesday May 01, 2013 @05:12PM (#5640824)
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?

Re:Go 1.1 RC1 is out by dylanvee on Wednesday May 01, 2013 @05:27PM (#5640907)
Marking the heap's region of memory as non-executable improves security. http://en.wikipedia.org/wiki/Executable_space_protection
Re:Go 1.1 RC1 is out by kristianp on Thursday May 02, 2013 @06:09PM (#5647502)
Sorry, I wasn't clearer, but I have heard of NX. The part I was wondering about was how the function representation changed.
Re:Go 1.1 RC1 is out by JulienSchmidt on Wednesday May 01, 2013 @05:35PM (#5640949)
http://en.wikipedia.org/wiki/NX_bit

Edit: dylanvee was faster, the NX-bit is the underlying hardware feature

Re:Go 1.1 RC1 is out by axw on Friday May 03, 2013 @12:02AM (#5648747)
The gory details are here: 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.