The following patch solves most of LRA scalability problems.
Itswitches on simpler algorithms in LRA. The first it switches off
trying to reassign hard registers to spilled pseudos (they usually for such
huge functions have long live ranges -- so the possibility to assign
them something very
On Thu, Oct 4, 2012 at 5:37 PM, Vladimir Makarov wrote:
> The only issue now is PR54146 compilation time for IRA+LRA although it
> was improved significantly. I will continue work on PR54146. But now I
> am going to focus on proposals from reviews.
Right, there still are opportunities to impr
On Thu, Oct 4, 2012 at 7:07 PM, Steven Bosscher wrote:
> On Thu, Oct 4, 2012 at 5:37 PM, Vladimir Makarov wrote:
>> The only issue now is PR54146 compilation time for IRA+LRA although it
>> was improved significantly. I will continue work on PR54146. But now I
>> am going to focus on proposal
On Thu, Oct 4, 2012 at 5:37 PM, Vladimir Makarov wrote:
> The following patch solves most of LRA scalability problems.
>
> It switches on simpler algorithms in LRA. The first it switches off
> trying to reassign hard registers to spilled pseudos (they usually for such
> huge functions have lon
On 12-10-10 10:53 AM, Steven Bosscher wrote:
On Thu, Oct 4, 2012 at 5:37 PM, Vladimir Makarov wrote:
The following patch solves most of LRA scalability problems.
It switches on simpler algorithms in LRA. The first it switches off
trying to reassign hard registers to spilled pseudos (they
On Wed, Oct 10, 2012 at 10:14 PM, Vladimir Makarov wrote:
> It is also interesting that your IRA range patch results in
> different code generation (i can not explain it too now). I saw the same
> on a small test (black jack playing and betting strategy).
I haven't looked into this, but I'm gue
