Create the page "Google Summer of Code 2013/cs648/" on this wiki! See also the search results found.
Page title matches
Suggest will take a week to read and understand the workings of cpc_runtime:
A good place to start is to examine the different stages of CPC translation (accessed with -stageX option)
1 KB (231 words) - 16:25, 21 June 2013
...rol state of the program. It contains the call stack of the current thread of execution along with the "stack variables" (in CPC they are stored on the h
...length of the stack and a '''size''' attribute which is the allocated size of the stack (it must be reallocated if pushing to it would exceed this size.
2 KB (324 words) - 18:22, 21 June 2013
'''Milestone:''' Write up a short explanation of the memory structures used by the CPC runtime
...s initial steps of the project, written up at [[Google_Summer_of_Code_2013/cs648/Initial_Meeting|Initial Meeting]]
972 B (146 words) - 20:59, 21 June 2013
...ext.c and added some features to the stub by basically copying and pasting code from coroutine-ucontext..c
* Fixed a few aspects of the prototype, so that it passes more tests.
876 B (123 words) - 00:06, 14 July 2013
'''Milestone:''' Have qemu-img and qemu-io completely working by the end of next week
* Analyse the performance of the CPC prototype compared to the ucontext implementation
758 B (105 words) - 01:35, 19 July 2013