This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: Your last commit to new-regalloc-branch


Daniel Berlin <dan@cgsoftware.com> writes:

> If this works, it means we need to fix regclass and regscan_update to
> just frickin work.
> We can't go redoing all of life analysis, all of register scanning,
> all of register usage, etc, on each pass.
> It's murder.

I'm agree with you. My patch significantly slowdown the new-allocator.
I don't apply my patch.

> reg_scan_update was specifically there for incremental updating when
> you emit new pseudos.
> If it doesn't work, we should fix it.


> max_regno was also correct given the circumstances. reg_scan_update
> wanted the previous max register (IE the max before we emitted new
> pseudos), so max_regno, having not been updated, was that number.

Yes yes.

Denis.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]