On Sun, Mar 13, 2016 at 05:54:58PM -0400, David Edelsohn wrote:
> Should the testcase go in g++.dg or gcc.target/powerpc?
I think it is a good thing to test everywhere, not just on Power.
Once we get it to work properly there will be no target-specific
anything left in the testcase, either.
On Sun, Mar 13, 2016 at 2:52 PM, Segher Boessenkool
wrote:
> On Sat, Mar 12, 2016 at 09:59:12AM -0500, David Edelsohn wrote:
>> > 2016-03-12 Segher Boessenkool
>> >
>> > PR target/70098
>> > * config/rs6000/rs6000.md
On Sat, Mar 12, 2016 at 09:59:12AM -0500, David Edelsohn wrote:
> > 2016-03-12 Segher Boessenkool
> >
> > PR target/70098
> > * config/rs6000/rs6000.md (*ctr_internal1,
> > *ctr_internal2,
> > *ctr_internal5, *ctr_internal6): Also allow "d"
On Sat, Mar 12, 2016 at 8:55 AM, Segher Boessenkool
wrote:
> In the rs6000 port, FLOAT_REGS can contain DImode values when compiling
> for 64-bit targets. Some instructions (like "fcfid" in the testcase,
> convert from integer to DP float) only work on floating point
In the rs6000 port, FLOAT_REGS can contain DImode values when compiling
for 64-bit targets. Some instructions (like "fcfid" in the testcase,
convert from integer to DP float) only work on floating point registers.
So, we do want to allow DImode in these regs.
Now, in unusual cases IRA will