Re: Different reload behavior from 4.3.3 to 4.4

2009-05-15 Thread Jamie Prescott
> From: Jamie Prescott > To: gcc@gcc.gnu.org > Sent: Friday, May 15, 2009 3:28:18 PM > Subject: Different reload behavior from 4.3.3 to 4.4 > > > In my VM, the X_REGS class is a generic 64bit regsiter class that can hold > both 64bit DImode and 64bit DFmode. > Such

Re: Different reload behavior from 4.3.3 to 4.4

2009-05-15 Thread Jamie Prescott
> From: Jamie Prescott > To: gcc@gcc.gnu.org > Sent: Friday, May 15, 2009 4:16:30 PM > Subject: Re: Different reload behavior from 4.3.3 to 4.4 > > > > From: Jamie Prescott > > To: gcc@gcc.gnu.org > > Sent: Friday, May 15, 2009 3:28:18 PM > > Subjec

Re: Different reload behavior from 4.3.3 to 4.4

2009-05-15 Thread Jamie Prescott
> From: Jamie Prescott > To: gcc@gcc.gnu.org > Sent: Friday, May 15, 2009 3:28:18 PM > Subject: Different reload behavior from 4.3.3 to 4.4 > > > In my VM, the X_REGS class is a generic 64bit regsiter class that can hold > both 64bit DImode and 64bit DFmode. > Such

Different reload behavior from 4.3.3 to 4.4

2009-05-15 Thread Jamie Prescott
In my VM, the X_REGS class is a generic 64bit regsiter class that can hold both 64bit DImode and 64bit DFmode. Such class does not allow direct constant loading, so in 4.3.3 I had: enum reg_class xxx_preferred_reload_class(rtx x, enum reg_class regclass) { enum machine_mode mode = GET_MOD