Re: virtual-stack-vars reference not resolved in vregs

> On May 25, 2018, at 2:11 AM, Eric Botcazou wrote: > >> Is this something the back end is responsible for getting right, for example >> via the machine description file? If so, any hints where to start? > > The SUBREG of MEM is invalid at this stage. Thanks. That

Re: virtual-stack-vars reference not resolved in vregs

On Fri, May 25, 2018 at 08:11:43AM +0200, Eric Botcazou wrote: > > Is this something the back end is responsible for getting right, for example > > via the machine description file? If so, any hints where to start? > > The SUBREG of MEM is invalid at this stage. >From rtl.texi: --- There are

Re: virtual-stack-vars reference not resolved in vregs

> Is this something the back end is responsible for getting right, for example > via the machine description file? If so, any hints where to start? The SUBREG of MEM is invalid at this stage. -- Eric Botcazou

virtual-stack-vars reference not resolved in vregs

I'm doing cleanup on the pdp11 back end to get rid of a number of ICE in the test suite. One is in gcc.c-torture/compile/20001221.c -- it works in GCC 4 but fails in GCC 5 and later. In the dumps, I see in the output from the expand phase a large number of memory reference via the