Re: Delimited continuations to the rescue of futures

2012-11-17 Thread Ludovic Courtès
Hi Mark, Mark H Weaver m...@netris.org skribis: l...@gnu.org (Ludovic Courtès) writes: As was reported recently by Mark and others, ‘par-map’ would only use ncores - 1, because the main thread was stuck in a ‘wait-condition-variable’ while touching one of the futures. The obvious fix is

CPS and RTL

2012-11-17 Thread Noah Lavine
Hello, I've had several conversations on this list about using continuation-passing style in Guile. I recently decided to take the hint and implement it. I've pushed a new branch called wip-rtl-cps that I'd appreciate comments on (but I do not necessarily think that this is the branch that will

Guile Lua

2012-11-17 Thread Ian Price
About two weeks ago, I emailed Phil, who had shown some interest in hacking guile lua a while back. I still haven't heard back from him, nor has that branch been touched in 18 months, so I think we can safely say we need a new maintainer for it. I have little knowledge of lua, so I can't really

Re: Delimited continuations to the rescue of futures

2012-11-17 Thread Mark H Weaver
Hi Ludovic, l...@gnu.org (Ludovic Courtès) writes: Mark H Weaver m...@netris.org skribis: In other words, if you have 4 cores and call 'par-map' on a list of 1000 elements, the main thread will only be used to process 1 out of 1000 elements, and only 3 cores will be used to process the other

register allocation

2012-11-17 Thread Stefan Israelsson Tampe
Hi all, If I've not miss - understood wingo's and Marks intention for native code, there need to be a intermediate format to output from tree-il that is different from the rtl bytecode. One of the reason's for this is that one need a better format in order to do register allocations well. What I

Re: Program received signal SIGSEGV, Segmentation fault.

2012-11-17 Thread Bruce Korb
On 11/16/12 20:22, Mark H Weaver wrote: Bruce, if you refuse to fix these problems properly, you will end up Hi Mark, My program's intent is to read text from two inputs and weave them together. It has no need to know or understand the encoding in any way, other than to communicate exception

Re: Program received signal SIGSEGV, Segmentation fault.

2012-11-17 Thread Mark H Weaver
Bruce Korb bk...@gnu.org writes: On 11/16/12 20:22, Mark H Weaver wrote: Bruce, if you refuse to fix these problems properly, you will end up Hi Mark, My program's intent is to read text from two inputs and weave them together. It has no need to know or understand the encoding in any way,

Re: CPS and RTL

2012-11-17 Thread Stefan Israelsson Tampe
Hi Noha, very clean code indeed, nice work, (mine rtl compiler is much more a bit of a hack btw :-)) One thing to think about from the beginning is how to protect variables from gc and at the same time offer unreachable vars to be gc:d at an early state. In guile-2.0 we kept using a stack for

Re: Program received signal SIGSEGV, Segmentation fault.

2012-11-17 Thread Bruce Korb
Hi Noah, Mark, On 11/16/12 18:19, Noah Lavine wrote: OK, so I tried latin1, too. (replacing scm_from_utf3_string with scm_from_latin1_string). That also does not work. It replaced the 0xA9 character with '?'. I am no expert on character encodings, but we've seen errors like

Re: Delimited continuations to the rescue of futures

2012-11-17 Thread Ludovic Courtès
Hi Mark! Mark H Weaver m...@netris.org skribis: I guess the one remaining concern I have is that if there are any long-running futures in the process, then any 'touch' could take a very long time to complete, even if the future it is waiting for is a very short job. For example, (par-map -