I've set up a new user on my laptop that we can use for experimenting
with benchmarks during Connect. Here's what we've got:
* A user called 'connect'
* Ramana, Ulrich, Åsa, and myself can log in via SSH
* bzr repo for trunk, 4.6, and gcc-linaro 4.6
* Tarballs of all gcc-linaro 4.4, 4.5, and 4
Hi guys,
I compile a native gdb using linaro 2011.10 by “./configure
--host=arm-none-linux-gnueabi --target=arm-none-linux-gnueabi”, and
the gdb runs on arm target boards directly.
# gdb
GNU gdb (Linaro GDB) 7.3-2011.10
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL versi
On 1 February 2012 23:08, Ramana Radhakrishnan
wrote:
> On 1 February 2012 19:33, Ulrich Weigand wrote:
>>
>> Ramana Radhakrishnan wrote on 01.02.2012
>> 16:28:04:
>>
>>> This patch should be queued for 4.8 .Sounds sensible to me.
>>
>> OK, thanks for the review!
>>
>>> > (As an aside, it might
On 1 February 2012 19:33, Ulrich Weigand wrote:
>
> Ramana Radhakrishnan wrote on 01.02.2012
> 16:28:04:
>
>> This patch should be queued for 4.8 .Sounds sensible to me.
>
> OK, thanks for the review!
>
>> > (As an aside, it might likewise be helpful to update the vec_set
> patterns
>> > to allow
On Wed, Feb 1, 2012 at 4:05 PM, Michael Hope wrote:
> On Wed, Feb 1, 2012 at 2:51 PM, Michael Hope wrote:
>> On Wed, Feb 1, 2012 at 7:09 AM, Christian Robottom Reis
>> wrote:
>>> On Tue, Jan 31, 2012 at 02:22:27PM +1300, Michael Hope wrote:
One of our cards this quarter was -O3 as a perfor
Ramana Radhakrishnan wrote on 01.02.2012
16:28:04:
> This patch should be queued for 4.8 .Sounds sensible to me.
OK, thanks for the review!
> > (As an aside, it might likewise be helpful to update the vec_set
patterns
> > to allow for memory operands, implemented via vld1.)
>
> Agreed.
The at
The Linaro Android team has scheduled an SMP session and is requesting
some participation from the Toolchain WG.
The session's blueprint to subscribe to:
https://blueprints.launchpad.net/linaro-android/+spec/linaro-platforms-q112-android-smp-on-android
Zach,
If this is not the correct session, ple
Hi Uli,
Thanks for the detailed analysis.
>
> The reason for this particular code sequence turns out to be as follows:
> The middle end tries to store the LSB vector lane to memory, and uses the
> vec_extract named pattern to do so. This pattern currently only supports
> an "s_register_operand"