Displaying 4 results from an estimated 4 matches for "264ref".
Did you mean:
h264ref
2011 Apr 03
3
[LLVMdev] [GSoC] Increase the coverage of Polly
...middle term paperwork.
6w Create tests for each of cases which are not currently optimized (e.g.
have min/max, sext/zext, trunc or unsigned comparisons in the loop bounds or
memory accesses).
7w Learn how optimization process work for this examples.
8-10w Enable tests one by one.
11w Estimate SPEC 264ref performnace improvement (yes, I have access to
one).
12w Complete paperwork.
I hope that it's real to complete this plan in time
26 марта 2011 г. 1:03 пользователь Tobias Grosser <grosser at fim.uni-passau.de
> написал:
> On 03/25/2011 05:44 PM, Vlad Krylov wrote:
>
>> Hel...
2011 Apr 05
0
[LLVMdev] [GSoC] Increase the coverage of Polly
...l represenation. Optimizers like Pluto will
automatically calculate the relevant optimizations, if you generate a
correct polyhedral representation.
> 8-10w Enable tests one by one.
By 'Enable tests' do you mean implementing support for min/max ..
expressions?
> 11w Estimate SPEC 264ref performnace improvement (yes, I have access to
> one).
What do you plan to measure exactly? Runtime performance?
I think another very interesting thing would be an analysis that shows
how much of the hot loops we can optimize. You can use such an analysis
also to estimate the possible speedup...
2011 Apr 05
0
[LLVMdev] doxygen build fails
...will automatically calculate
> the relevant optimizations, if you generate a correct polyhedral
> representation.
>
>> 8-10w Enable tests one by one.
>
> By 'Enable tests' do you mean implementing support for min/max ..
> expressions?
>
>> 11w Estimate SPEC 264ref performnace improvement (yes, I have access to
>> one).
>
> What do you plan to measure exactly? Runtime performance?
>
> I think another very interesting thing would be an analysis that shows how
> much of the hot loops we can optimize. You can use such an analysis also to
>...
2011 Apr 07
3
[LLVMdev] [GSoC] Increase the coverage of Polly
...will automatically calculate
> the relevant optimizations, if you generate a correct polyhedral
> representation.
>
>> 8-10w Enable tests one by one.
>
> By 'Enable tests' do you mean implementing support for min/max ..
> expressions?
>
>> 11w Estimate SPEC 264ref performnace improvement (yes, I have access to
>> one).
>
> What do you plan to measure exactly? Runtime performance?
>
> I think another very interesting thing would be an analysis that shows how
> much of the hot loops we can optimize. You can use such an analysis also to
>...