search for: _exposing_

...resource > class as memory :-) Chris, LLVMers, could you allocate CPUs resources as > you do it for registers and memory? :P Our mid-term plans include looking at multithreading/parallel processing kinds of things, at least for shared memory systems. At the LLVM level, we are interested in _exposing_ parallelism. In the fib example you are using, for example, it is pretty easy to show that all of the subcalls to fib can be run independently of each other (ie, in parallel). Combined with a suitable runtime library (e.g., pthreads), you could imagine an LLVM transformation that allows it to run...

...CL> Our mid-term plans include looking at multithreading/parallel processing CL> kinds of things, at least for shared memory systems. cool... guys, I pray you get your "financial air" on a regular basis! what you do is very important. CL> At the LLVM level, we are interested in _exposing_ parallelism. hm... strange. You mean, you going to define explicitly what and how to parallelize? Why then we don't need similar unpleasant things for registers?.. CL> In the fib example you are CL> using, for example, it is pretty easy to show that all of the subcalls to CL> fib ca...

> I see more precisely what you mean, but I don't think it is that > straightforward to generalise the benefits multiple CPU on single host > programming to multiple CPU at multiple hosts. I don't think that both > cases involve the same techniques. you are right, just think of shared memory. > For example, in "single host" configuration you get a very low

Hello again Valery, Valery A.Khamenya wrote: > All benefits, what one could obtain from "LLVM supporting multiple CPU > at single host", one might obtaine from "LLVM supporting multiple CPU > at multiple hosts". Isn't that logical? I see more precisely what you mean, but I don't think it is that straightforward to generalise the benefits multiple CPU on