Displaying 3 results from an estimated 3 matches for "state_end".
Did you mean:
stack_end
2012 Dec 01
6
[LLVMdev] [RFC] "noclone" function attribute
...nd would produce a state machine and a loop similar to this:
while (1) {
switch (state) {
case STATE_START:
for (x...) for (y...) for (z...)
state = kernel_START(x, y, z);
break;
case STATE_BARRIER1:
for (x...) for (y...) for (z...)
state = kernel_BARRIER1(x, y, z);
break;
case STATE_END:
return;
}
}
where every kernel sub-function (kernel_START and kernel_BARRIER1 in this example) return a new state.
Notice this relies upon all calls to either kernel_START or kernel_BARRIER1 returning the *same* next state. This is guaranteed by the OpenCL spec.
Let's apply jump threading...
2012 Dec 02
0
[LLVMdev] [RFC] "noclone" function attribute
...nd would produce a state machine and a loop similar to this:
while (1) {
switch (state) {
case STATE_START:
for (x...) for (y...) for (z...)
state = kernel_START(x, y, z);
break;
case STATE_BARRIER1:
for (x...) for (y...) for (z...)
state = kernel_BARRIER1(x, y, z);
break;
case STATE_END:
return;
}
}
where every kernel sub-function (kernel_START and kernel_BARRIER1 in this example) return a new state.
Notice this relies upon all calls to either kernel_START or kernel_BARRIER1 returning the *same* next state. This is guaranteed by the OpenCL spec.
Let's apply jump threading...
2015 Feb 05
5
[LLVMdev] RFC: Recursive inlining
Hi,
The other day on IRC myself, Chandler, Hal and Pablo discussed recursive
inlining. I've pondered a bit since then, and thought I'd get some
background on the list with the aim of stimulating discussion.
Our goal is to inline recursive functions. We have several workloads with
recursive calls, and inlining them to a certain degree can improve
performance by up to 30%.
Inlining