Sure. I'd very glad to share. Here' s my git repo which is a fork from the upstream of plt (probably out of sync for a couple of weeks).<div><a href="https://github.com/nevo/racket-hack">https://github.com/nevo/racket-hack</a></div> <div><br></div><div>If you'd want me to prepare standalone patches, please let me know.</div><div>I'd be much appreciated for your contribution. Thanks!</div><div><br></div><div>Nevo</div><div><br><div class="gmail_quote"> On 26 April 2011 10:22, Kevin Tew <span dir="ltr"><<a href="mailto:tewk@cs.utah.edu">tewk@cs.utah.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> <div text="#000000" bgcolor="#FFFFFF"> If your willing, we would like to see your code changes/patches get integrated back into the project.<br> This is the best way to get more developers interested and willing to work on Racket for iOS.<br> <br> Are you willing to share your changes?<br> We are willing to take them in any form, clean them up, and get them committed.<br><font color="#888888"> <br> Kevin</font><div><div></div><div class="h5"><br> <br> <br> On 04/25/2011 06:15 PM, Nevo wrote: <blockquote type="cite">hi Kevin: <div> I've successfully enabled places with a few in-code fix to be compiler happy, mostly are implement atomic operations using OSAtomicXXX provided by Apple and emit arm instruction instead of thumb. It just run without low memory crashes (at least per my recent runs), although still getting a level 1 memory warning which is common for most of complicated softwares in iOS I think. But I would be rather appreciated if you have something else which I can look into by myself to further reduce memory consumption. Thanks!</div> <div><br> </div> <div>Cheers</div> <div>Nevo<br> <br> <div class="gmail_quote">On 23 April 2011 21:24, Nevo <span dir="ltr"><<a href="mailto:sakur.deagod@gmail.com" target="_blank">sakur.deagod@gmail.com</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> hi Kevin: <div> Thanks for your help here. I'm trying to enable "place" first then I think I can apply your patch. Is there still a way to reduce unused memory as in your patch, but without the need of "place"?</div> <div><br> </div> <div><font color="#888888">Nevo</font> <div> <div><br> <br> <div class="gmail_quote">On 23 April 2011 21:16, Kevin Tew <span dir="ltr"><<a href="mailto:tewk@cs.utah.edu" target="_blank">tewk@cs.utah.edu</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Here is another patch you can try to reduce caching of unused memory.<br> <br> diff --git a/src/racket/gc2/alloc_cache.c b/src/racket/gc2/alloc_cache.c<br> index 44895af..d1f1c03 100644<br> --- a/src/racket/gc2/alloc_cache.c<br> +++ b/src/racket/gc2/alloc_cache.c<br> @@ -10,7 +10,7 @@<br> */<br> <br> /* Controls how often freed pages are actually returned to OS: */<br> -#define BLOCKFREE_UNMAP_AGE 3<br> +#define BLOCKFREE_UNMAP_AGE 0<br> <br> /* Controls size of the cache */<br> #define BLOCKFREE_CACHE_SIZE 3000 <div> <div><br> <br> <br> On 04/23/2011 05:14 AM, Jens Axel Søgaard wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> 2011/4/22 Nevo<<a href="mailto:sakur.deagod@gmail.com" target="_blank">sakur.deagod@gmail.com</a>>:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> hi<br> My attempt on porting Racket interpreter to iOS has been for a while and<br> I've been able to run interpreter on both iOS device as well iOS simulator.<br> </blockquote> Great news.<br> <br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Right now, it runs perfectly on iOS simulator, but lack of satisfaction on<br> device. The reason is for those devices like iPad/iPhone or Android, the<br> memory for standalone application is always constrained, and even a single<br> "hello world" evaluation would easily put the whole app runtime to death,<br> per my test.<br> </blockquote> I am curious which iPhone and which iPad?<br> <br> For the non-iPad owners here are a few (unofficial) specs, so you<br> have a rough idea of how much memory the iDevices have:<br> <br> Internal RAM for:<br> iPad 2 512MB<br> iPad 1 256MB<br> <br> iPhone 4 512MB<br> iPhone 3GS 256MB<br> iPhone 3G 128MB<br> iPhone 128MB<br> <br> </blockquote> <br> </div> </div> </blockquote> </div> <br> </div> </div> </div> </blockquote> </div> <br> </div> </blockquote> <br> </div></div></div> </blockquote></div><br></div>