[reload-v2] Fix bootstrap problems after last merge

Jeff Law law@redhat.com
Thu Jun 10 06:45:00 GMT 2010


This fixes various minor problems bootstrapping after this week's merge 
from the trunk to the reload-v2 branch.  One issue was 
ira_bad_reload_regno was integrated onto the trunk and we had a 
duplicate definition on the branch.  With Bernd's recent patch we're 
seeing some allocnos with NO_REGS appearing more often, which can lead 
to problems because there is no cost_vector_pool created for NO_REGS.  
Finally we don't want to wipe the reg_equiv_memory_loc state when 
ira-reload calls back into ira_costs.

The problems with allocnos preferring NO_REGS is something that I'm 
still looking at -- for the case I'm working on we really just want a 
GENERAL_REG, but are punting to NO_REGS for reasons unknown.


-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: PP
URL: <http://gcc.gnu.org/pipermail/gcc-patches/attachments/20100610/97603612/attachment.ksh>


More information about the Gcc-patches mailing list