IssueRaiser

C doesn't make for an optimal backend, due to issues like: - no proper tail calls - no way to cheaply check if arithmetic has overflowe...

C doesn't make for an optimal backend, due to issues like: - no proper tail calls - no way to cheaply check if arithmetic has overflowed, so performant arbitrary-precision integers are hard to implement - hard to find GC roots on C stack C-- is a better portable assembly language that was designed for such purposes. http://www.cminusminus.org/ Unfortunately it looks like it hasn't found wider adoption (except for GHC), similar to MLRISC.

Posted by the_why_of_y on Apr 6, 2015, 11:49 AM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.7,500 issues0 comments

ux (Other)

C doesn't make for an optimal backend, due to issues like: - no proper tail calls - no way to cheaply check if arithmetic has overflowe...

the_why_of_yApr 6, 2015, 11:49 AM

C doesn't make for an optimal backend, due to issues like: - no proper tail calls - no way to cheaply check if arithmetic has overflowed, so performant arbitrary-precision integers are hard to implement - hard to find GC roots on C stack C-- is a better portable assembly language that was designed for such purposes. http://www.cminusminus.org/ Unfortunately it looks like it hasn't found wider adoption (except for GHC), similar to MLRISC.

Comments (0)

No comments yet. Start the discussion.

Comment on this issue