Re: GCC Optimization Brain Storming Session

2010-12-09 Thread Peter Maydell
On 9 December 2010 21:51, Ramana Radhakrishnan wrote: > On 9 Dec 2010, at 15:19, "Julian Brown" wrote: >>  * Load/store multiple instructions: GCC only generates these from >>    load_multiple/store_multiple (from a couple of places where hard >>    registers are already known, e.g. function prol

Re: GCC Optimization Brain Storming Session

2010-12-09 Thread Ramana Radhakrishnan
Hit send accidentally on my last mail. Sorry On 9 Dec 2010, at 15:19, "Julian Brown" wrote: > On Thu, 09 Dec 2010 14:42:49 + > Andrew Stubbs wrote: > >> On 26/11/10 11:11, Andrew Stubbs wrote: >>> As we discussed on Monday, I think it might be helpful to get a >>> number of knowledgeable

Re: GCC Optimization Brain Storming Session

2010-12-09 Thread Ramana Radhakrishnan
Sent from my iPad On 9 Dec 2010, at 15:19, "Julian Brown" wrote: > On Thu, 09 Dec 2010 14:42:49 + > Andrew Stubbs wrote: > >> On 26/11/10 11:11, Andrew Stubbs wrote: >>> As we discussed on Monday, I think it might be helpful to get a >>> number of knowledgeable people together on a call

Re: GCC Optimization Brain Storming Session

2010-12-09 Thread Julian Brown
On Thu, 09 Dec 2010 14:42:49 + Andrew Stubbs wrote: > On 26/11/10 11:11, Andrew Stubbs wrote: > > As we discussed on Monday, I think it might be helpful to get a > > number of knowledgeable people together on a call to discuss GCC > > optimization opportunities. > > > > So, I'd like to get so

Re: GCC Optimization Brain Storming Session

2010-12-09 Thread Mark Mitchell
On 12/9/2010 6:42 AM, Andrew Stubbs wrote: > Either Wednesday 15th December at 9am UTC > Or Thursday 16th 6pm UTC > > If selected these times so that Michael can attend. Obviously the former > is more palatable to Europeans, and the latter allows Americans to join, > if we have any inte

Re: GCC Optimization Brain Storming Session

2010-12-09 Thread Andrew Stubbs
On 26/11/10 11:11, Andrew Stubbs wrote: As we discussed on Monday, I think it might be helpful to get a number of knowledgeable people together on a call to discuss GCC optimization opportunities. So, I'd like to get some idea of who would like to attend, and we'll try to find a slot we can all

Re: GCC Optimization Brain Storming Session

2010-11-29 Thread Steven Bosscher
Andrew Stubbs wrote: > * Instruction set coverage. > - Are there any ARM/Thumb2 instructions that we are not taking > advantage of? [2] > - Do we test that we use the instructions we do have? [3] There is no general frame work to test instruction set coverage. The only way to find out, r

Re: GCC Optimization Brain Storming Session

2010-11-29 Thread David Gilbert
On 29 November 2010 00:18, Michael Hope wrote: > > To add to the mix: > > Some ideas that are logged as blueprints: > Using ARMv5 saturated instructions > (https://blueprints.launchpad.net/gcc-linaro/+spec/armv5-saturated-ops) > Using ARMv6 SIMD instructions > (https://blueprints.launchpad.net/

Re: GCC Optimization Brain Storming Session

2010-11-28 Thread Michael Hope
On Sat, Nov 27, 2010 at 12:11 AM, Andrew Stubbs wrote: > Hi All, > > As we discussed on Monday, I think it might be helpful to get a number of > knowledgeable people together on a call to discuss GCC optimization > opportunities. > > So, I'd like to get some idea of who would like to attend, and w

Re: GCC Optimization Brain Storming Session

2010-11-26 Thread Christian Robottom Reis
On Fri, Nov 26, 2010 at 10:40:34AM -0800, Mark Mitchell wrote: > As an extension of that idea, and tying into the idea of optimizing for > size, I suspect that we (a) ought be optimizing for size automatically > in cold code, and (b) that we're probably not doing a great job of > optimizing for siz

Re: GCC Optimization Brain Storming Session

2010-11-26 Thread Mark Mitchell
On 11/26/2010 3:11 AM, Andrew Stubbs wrote: > As we discussed on Monday, I think it might be helpful to get a number > of knowledgeable people together on a call to discuss GCC optimization > opportunities. I'm not sure I qualify as knowledgeable, and my schedule is a mess, so please don't try to