25,360 karma · joined December 4, 2014
http://austinhenley.com
Check out my blog post, Challenging projects every programmer should try:
https://dl.acm.org/doi/pdf/10.1145/800181.810318?casa_token=...
> BEAM/C generated a single C function for each Erlang module. Local calls within the module were made by explicitly pushing the return address to the Erlang stack followed by a goto to the label of the called function. (Strictly speaking, the calling function stores the return address to BEAM register and the called function pushes that register to the stack.)
> Calls to other modules were done similarly by using the GCC extension that makes it possible to take the address of a label and later jumping to it. Thus an external call was made by pushing the return address to the stack followed by a goto to the address of a label in another C function.
> Isn’t that undefined behavior?
> Yes, it is undefined behavior even in GCC.
Basically: tell me how long it took other people.
Happening to other people too: https://www.macrumors.com/2020/11/12/macos-big-sur-download-...
I think something like that could do really well now since there seems to be so much interest in the topic now based on all the Reddit and HN posts.