Displaying 4 results from an estimated 4 matches for "some_rare_condit".
2015 Jan 08
9
[LLVMdev] Separating loop nests based on profile information?
...mization to separate a single loop with multiple latches into
a loop nest, but I want to get feedback from interested parties before
investing much more effort.
The primary case I'm concerned about looks something like this C example:
while( some_condition )
//do lots of work here
if (!some_rare_condition) { <-- This is loop variant
helper();
}
}
The key point here is that the 'do lots of work' section contains things
we could lift out of the loop, but our knowledge of memory gets
completely destoryed by the 'helper' call which doesn't get inlined.
This ends up...
2015 Jan 08
4
[LLVMdev] Separating loop nests based on profile information?
...loop nest, but I want to
> get feedback from interested parties before investing much more
> effort.
>
> The primary case I'm concerned about looks something like this C
> example:
> while( some_condition )
> //do lots of work here
> if (!some_rare_condition) { <-- This is loop variant
> helper();
> }
> }
>
> The key point here is that the 'do lots of work' section contains
> things we could lift out of the loop, but our knowledge of memory
> gets completely destoryed by the 'helper...
2015 Jan 13
2
[LLVMdev] Separating loop nests based on profile information?
...nto a loop
>> nest, but I want to get feedback from interested parties before investing
>> much more effort.
>>
>> The primary case I'm concerned about looks something like this C example:
>> while( some_condition )
>> //do lots of work here
>> if (!some_rare_condition) { <-- This is loop variant
>> helper();
>> }
>> }
>>
>> The key point here is that the 'do lots of work' section contains things
>> we could lift out of the loop, but our knowledge of memory gets completely
>> destoryed by the 'help...
2015 Jan 08
2
[LLVMdev] Separating loop nests based on profile information?
...single loop with multiple latches into a loop nest, but I want to get feedback from interested parties before investing much more effort.
>
> The primary case I'm concerned about looks something like this C example:
> while( some_condition )
> //do lots of work here
> if (!some_rare_condition) { <-- This is loop variant
> helper();
> }
> }
>
> The key point here is that the 'do lots of work' section contains things we could lift out of the loop, but our knowledge of memory gets completely destoryed by the 'helper' call which doesn't get in...