Re: [PR49888, VTA] don't keep VALUEs bound to modified MEMs

2012-06-15 Thread Alexandre Oliva
On Jun 14, 2012, "H.J. Lu" wrote: > On Tue, Jun 12, 2012 at 1:42 PM, Richard Henderson wrote: >> On 2012-06-05 12:33, Alexandre Oliva wrote: >>> for  gcc/ChangeLog >>> from  Alexandre Oliva   >>> >>>       PR debug/49888 >>>       * var-tracking.c: Include alias.h. >>>       (overlapping_mems):

Re: long long availability in host compiler (Re: constant that doesn't fit in 32bits in alpha.c)

2012-06-15 Thread Mike Stump
On Jun 15, 2012, at 2:46 PM, Joseph S. Myers wrote: > HOST_WIDE_INT is an abstraction about the *target*; the target determines > the required properties. The salient properties include: > > * At least as wide as target address space. The first person to do a 128 bit address support isn't going

Re: [RFC 0/3] Stuff related to pr53533

2012-06-15 Thread H.J. Lu
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

[lra] patch to improve live-range splitting

2012-06-15 Thread Vladimir Makarov
The following patch improves splitting heuristic (and overall SPEC2000 performance). The previous one was aggressive for local pseudos. We don't need to split local pseudo ranges as inheritance works well for them and achieves the same results. The patch was successfully bootstrapped on x86/

Re: long long availability in host compiler (Re: constant that doesn't fit in 32bits in alpha.c)

2012-06-15 Thread Joseph S. Myers
On Fri, 15 Jun 2012, Mike Stump wrote: > On Jun 15, 2012, at 2:46 PM, Joseph S. Myers wrote: > > HOST_WIDE_INT is an abstraction about the *target*; the target determines > > the required properties. The salient properties include: > > > > * At least as wide as target address space. > > The fi

<    1   2