GCC 4.6 BZR branch

2010-12-18 Thread Andrew Stubbs
You may have noticed that I have created a new BZR/Launchpad branch for 
Linaro GCC 4.6:


 lp:gcc-linaro/4.6

 https://code.launchpad.net/~linaro-toolchain-dev/gcc-linaro/4.6

Up until now, this has not been buildable due to unfixed bugs. However, 
upstream GCC have now straightened out the problems, so I have pushed a 
buildable version into the branch.


I shall attempt to keep this branch as up-to-date as I can (at least, I 
will once the holiday season and January travel are over), but I'll only 
push updates if they build for me, so hopefully the branch should remain 
fairly stable, at least for our purposes.


Note that so far I've only tested build-ability. Right now I'm not 
making any promises about the quality of the compiler.


At some point, we'll want to use this branch to hold our own patches 
(both those that will never go upstream, and those that are queued for 
GCC 4.7), so it will diverge from upstream 4.6 a bit. For the moment, 
it's merely a mirror.


Andrew

___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain


Re: [ACTIVITY] December 12 - 16

2010-12-18 Thread Ira Rosen
Hi Ramana,

On 16 December 2010 20:11, Ramana Radhakrishnan
 wrote:
> 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 for vectorization ?
>
> >From some research that Tejas did earlier this year, I thought that
> viterbi was among the hardest to vectorize because in addition to what
> you mention we need to support vld/st2 or (ofcourse vzip and vld1 if we
> don't support vld2) instructions and the other vbif / vbsl instructions
> to support vectorization for viterbi.

Right, we need vld2 and vst2 for Viterbi, and we are working on their
implementation (see this thread for the latest discussion
http://lists.linaro.org/pipermail/linaro-toolchain/2010-December/000540.html).

>
> I see that we support v in the backend now but we don't support
> the vector bitfield instructions like vbit / vbif and vbsl which can be
> used for vector select other than through intrinsics.

I haven't checked this. But in any case vector select is very
important and it's a good idea to support it anyway.

Ira

>
> I could be of-course missing something here 
>
> cheers
> Ramana
>
>
>
>>
>> Ira
>>
>> ___
>> linaro-toolchain mailing list
>> linaro-toolchain@lists.linaro.org
>> http://lists.linaro.org/mailman/listinfo/linaro-toolchain
>
>
>

___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain


[ACTIVITY] 13th -18th December 2010

2010-12-18 Thread Andrew Stubbs

* Linaro GCC

lp:686381: C++ link failure on ARM
Reproduced the bug and posted my findings to the bug report - user error.

Changed the way the Linaro GCC version numbers are handled. Hopefully 
the new system should be less distasteful to Matthias. Updated the GCC 
release procedure document to match.


Organised and chaired a meeting to discuss GCC optimization 
opportunities for ARM. It was well attended, and I think we had some 
useful discussion. Spend quite some time preparing beforehand, and 
writing it up afterwards. Next step is to come up with some actual plans 
to implement something. I imagine we can discuss this at the sprint in 
Dallas next month. See 
https://wiki.linaro.org/AndrewStubbs/Sandbox/GCCoptimizations




* Upstream GCC

My upstream patch to fix ARM smlabb has been approved and committed to 
GCC 4.6 (mainline). Only another three patches need approval now!


Continued testing upstream GCC 4.6 with both cross and native builds. It 
appears to be in a buildable state now, with no extra patches required. 
I've updated the Linaro GCC 4.6 branch with the buildable state.




* Other

Updated my ESTA, and added my security details to the airline bookings.


--
Future availability
20th Dec ..  3rd Jan - Vacation/Holiday
 4th Jan ..  8th Jan - Business as usual
 9th Jan .. 14th Jan - Linaro Sprint, Dallas
15th Jan .. 21st Jan - CodeSourcery/Mentor Annual Meeting, Scottsdale
24th Jan onwards - normal service restored!

___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain