Hi,
In case this is useful in its current (unfinished!) form: here are some
notes I made whilst looking at a couple of the items listed for CS308
here:
https://wiki.linaro.org/Internal/Contractors/CodeSourcery
Namely:
* automatic vector size selection (it's currently selected by command
On 15/09/10 10:37, Julian Brown wrote:
> The "vect256" branch now has a vectorization factor argument for
> UNITS_PER_SIMD_WORD (allowing selection of different vector sizes).
> Patches to support that would need backporting to 4.5 if that looks
> useful. Could investigate the feasibility of doing
* Goal
Goal of this work is to look for thumb2 code size improvements on FSF
GCC trunk.
* Methodology
** Build FSF GCC trunk w/ and wo/ hardfp, run benchmarks including
eembc, spec2000, and dhrystone, and check asm code to see if there is
any possible improvements on size.
** Get input and s
Hi,
> Also available is an early release of optimised string routines for
> the Cortex-A series, including a mix of NEON and Thumb-2 versions of
> memcpy(), memset(), strcpy(), strcmp(), and strlen(). For more
> information see:
> https://launchpad.net/cortex-strings
My understanding is that th
> > Linaro toolchain doesn't target a specific platform but is generic
> for armv7 platforms. Are you expecting to see those optimisations
> turned on in Linaro toolchain?
>
> Sorry, I don't understand the question. We want to spread these
> routines out and get them integrated into all of the ups
Hi,
I need to learn much more about ARM architecture, but I have some initial
comments.
Julian Brown wrote on 15/09/2010 11:37:21 AM:
> * automatic vector size selection (it's currently selected by command
> line switch)
> Generally (check assumption) I think that wider vectors may make
On 15/09/10 14:49, Yao Qi wrote:
> * Goal
>Goal of this work is to look for thumb2 code size improvements on FSF
> GCC trunk.
Thank you Yao, I think we've definitely got some things we can do good
work on here. :)
Andrew
___
linaro-toolchain maili
