search for: foo_kernel

...gt; For example, you have two functions and one calls the other: > > kernel foo() { > } > kernel bar() { > foo(); > } > > If you separate kernel function from the function body, then handling this becomes easy. > > You end up with four functions: > > kernel foo_kernel() { > foo(); > } > > foo() { > } > > kernel bar_kernel() { > bar(); > } > > bar(){ > foo(); > } > > Then the issue is no longer a compilation problem, but just an entry point runtime issue. Instead of calling foo(), the runtime just calls foo_kern...

...d everything from the device goes to the original entry point. For example, you have two functions and one calls the other: kernel foo() { } kernel bar() { foo(); } If you separate kernel function from the function body, then handling this becomes easy. You end up with four functions: kernel foo_kernel() { foo(); } foo() { } kernel bar_kernel() { bar(); } bar(){ foo(); } Then the issue is no longer a compilation problem, but just an entry point runtime issue. Instead of calling foo(), the runtime just calls foo_kernel() which handles all of the kernel setup issues and then calls the functi...

On Tue, Dec 21, 2010 at 07:17:40PM -0000, Anton Lokhmotov wrote: > > From: Peter Collingbourne [mailto:peter at pcc.me.uk] > > Sent: 20 December 2010 20:11 > > As with __local variables, it may be that "kernelness" cannot be > > represented in a standard form in LLVM. For example on a CPU a > > kernel function may have an additional parameter which is a