| cde | hai | 09:43 |
|---|---|---|
| lekernel | hi | 09:44 |
| sb0 | hm, why is struct sched_ctx so big... | 20:24 |
| wpwrak | sb0: it has a bunch of pointers and integers for each instruction | 21:05 |
| wpwrak | sb0: on 64 bit, it's even almost half a megabyte :) | 21:06 |
| wpwrak | on 64 bit, each instruction has a 216 bytes data structure. and there are up to 2048 instructions ... | 21:09 |
| wpwrak | (FPVM_MAXCODELEN) | 21:09 |
| wpwrak | the 216 bytes structure is struct insn | 21:10 |
| sb0 | ok | 21:21 |
| sb0 | well, currently FN is only using about 25MB out of the 128MB of the M1, so we can bloat it a little :-) | 21:22 |
| wpwrak | hehe :) | 21:22 |
| wpwrak | ah yes, a bigger stack helps :) | 21:23 |
| wpwrak | so the things in malloc.c don't work in the demo firmware ? | 21:24 |
| sb0 | they work | 21:32 |
| sb0 | you can use malloc() if you want... but try to avoid the non-reentrant global variable for the state | 21:33 |
| wpwrak | ah, so you expect to use this from threads | 21:35 |
| sb0 | using the stack is fine... if you have working code with the stack atm, don't change it | 21:39 |
| wpwrak | yeah, right now i have it with the stack. need to get rid of the global "sc", though | 21:40 |
| sb0 | struct vm_reg regs[frag->nbindings-frag->next_sur]; ? :) | 22:49 |
| wpwrak | mmh ? dynamic arrays. available since C99 :) | 23:09 |
| wpwrak | btw, i only tested with FN, not with the demo. still need to work on the prerequisites of it. | 23:12 |
| wpwrak | and now, off to the next barbecue :) | 23:12 |
| --- Mon Oct 3 2011 | 00:00 | |
Generated by irclog2html.py 2.9.2 by Marius Gedminas - find it at mg.pov.lt!