Displaying 4 results from an estimated 4 matches for "bigloop".
2015 Dec 04
2
Field sensitive alias analysis?
...ode and came across a situation where
invariant code is not being moved out:
On an -O3 compilation, I noticed that the "load" for the loop bounds (which
remain invariant throughout) happens on each iteration of both the loops,
even though it is not modified anywhere in the function "bigLoop". It seems
that alias analysis is not able to say that the writes to one field in the
structure does not impact the other field, leading to LICM being
ineffective.
Do any of the alias analyses currently have some kind of field sensitivity
that can help in this case?
-------------------------...
2015 Dec 07
3
Field sensitive alias analysis?
...t; invariant code is not being moved out:
>>
>> On an -O3 compilation, I noticed that the "load" for the loop bounds
>> (which remain invariant throughout) happens on each iteration of both the
>> loops, even though it is not modified anywhere in the function "bigLoop".
>> It seems that alias analysis is not able to say that the writes to one
>> field in the structure does not impact the other field, leading to LICM
>> being ineffective.
>>
>> Do any of the alias analyses currently have some kind of field
>> sensitivity t...
2015 Dec 08
2
Field sensitive alias analysis?
...oved out:
>>>>
>>>> On an -O3 compilation, I noticed that the "load" for the loop bounds
>>>> (which remain invariant throughout) happens on each iteration of both the
>>>> loops, even though it is not modified anywhere in the function "bigLoop".
>>>> It seems that alias analysis is not able to say that the writes to one
>>>> field in the structure does not impact the other field, leading to LICM
>>>> being ineffective.
>>>>
>>>> Do any of the alias analyses currently have s...
2015 Dec 09
2
Field sensitive alias analysis?
...t;
>>>>>> On an -O3 compilation, I noticed that the "load" for the loop bounds
>>>>>> (which remain invariant throughout) happens on each iteration of both the
>>>>>> loops, even though it is not modified anywhere in the function "bigLoop".
>>>>>> It seems that alias analysis is not able to say that the writes to one
>>>>>> field in the structure does not impact the other field, leading to LICM
>>>>>> being ineffective.
>>>>>>
>>>>>> Do an...