Hi there. I've cancelled the weekly and standup calls for the next
two weeks. The next scheduled call is the standup call on Wednesday
the 5th of January. Please attend if you can as it's our last one
before the sprint.
See you then!
-- Michael
___
Hi there. The sprint is just around the corner and it's a good time
to think about how we can make best use of the week. I've put some
topics up at:
https://wiki.linaro.org/Events/2011-01-LinaroSprint/ToolChainWG
Please feel free to add to it. Have a think about anything that's
easier to do wh
Hi Ira,
On Thu, 2010-12-16 at 15:29 +0200, Ira Rosen wrote:
> - telecom viterbi (vectorization potential gain is 4x) requires
> conditional store sinking and load hoisting to enable if-conversion. I
> worked on implementation of store sinking this week.
Is this the only feature that viterbi needs
RAG:
Red:
Amber:
Green:
Milestones:
| Planned| Estimate | Actual |
finish virtio-system | 2010-08-27 | postponed ||
get valgrind into linaro PPA | 2010-09-15 | 2010-09-28 | 2010-09-28 |
complete a qemu-maemo update | 2010-09-24 | 2010-09-
On 12/16/2010 6:25 AM, David Gilbert wrote:
> If Profile Guiding could spot that a particular callsite to say strlen()
> was often associated with strings
> of at least 'n' characters we could call a different implementation.
I don't believe this is possible current profile-guided optimization,
b
Does anyone have any experience of what can be profiled in the profiled
guided optimisations?
One of the problems with some of the string routines is that you can write
pretty neat fast routines that
work well for long strings - but most of the calls actually pass short
strings and the overhead of
Hi,
* I've spent some time for testing the patches that allow the GCC trunk
to bootstrap again on ARM and posted the results to gcc-testresults
* finally tested and posted the patch that optimizes the __sync_*
builtins (#681138) on gcc-patches
* investigated on the state of the crash uti
Hi,
I continued looking into EEMBC benchmarks:
- telecom fft is not vectorized because unknown number of iterations.
It has both non-constant step and its loop bound may overflow. I
think, the solution here could be loop versioning, but since
versioning increases code size, this kind of optimizati
