On 2012-06-19 15:55, Matt wrote:
> On 2012-06-15 13:57, Richard Henderson wrote:
>> > Bootstrapped and tested on x86_64, but I'll leave some time for
>> > comment before committing any of this.
>
>> Patches now committed.
>
> Hey Richard,
>
> Thanks for taking on some of these issues. I'm not se
On 2012-06-15 13:57, Richard Henderson wrote:
> Bootstrapped and tested on x86_64, but I'll leave some time for
> comment before committing any of this.
Patches now committed.
Hey Richard,
Thanks for taking on some of these issues. I'm not seeing much of an
improvement yet when manually ap
On 2012-06-15 13:57, Richard Henderson wrote:
> Bootstrapped and tested on x86_64, but I'll leave some time for
> comment before committing any of this.
Patches now committed.
r~
On Fri, 15 Jun 2012, Richard Henderson wrote:
> ... but not actually fixing it.
>
> I was hoping that the first patch might give the vectorizer enough
> info to solve the costing problem, but no such luck. Nevertheless
> it would seem that not having the info present at all would be a
> bit of a
On Fri, Jun 15, 2012 at 3:06 PM, Richard Henderson wrote:
> On 2012-06-15 14:42, H.J. Lu wrote:
>> Latency/throughput info is in Intel optimization reference manual.
>> Which instructions aren't covered?
>
> Ok, good. The rather old opt ref manual that I had didn't cover these.
> The one I downlo
On 2012-06-15 14:42, H.J. Lu wrote:
> Latency/throughput info is in Intel optimization reference manual.
> Which instructions aren't covered?
Ok, good. The rather old opt ref manual that I had didn't cover these.
The one I downloaded this afternoon does. And it seems that we would
need new costs
On Fri, Jun 15, 2012 at 1:57 PM, Richard Henderson wrote:
> ... but not actually fixing it.
>
> I was hoping that the first patch might give the vectorizer enough
> info to solve the costing problem, but no such luck. Nevertheless
> it would seem that not having the info present at all would be a
... but not actually fixing it.
I was hoping that the first patch might give the vectorizer enough
info to solve the costing problem, but no such luck. Nevertheless
it would seem that not having the info present at all would be a
bit of a hindrence when actually tweeking the vectorizer later...
