On Sat, Jun 03, 2017 at 12:34:21PM +0200, Eric Botcazou wrote:
> > Because you cannot during reload, or another reason? We always use LRA
> > on powerpc nowadays, and LRA can deal with this.
>
> Because you cannot during prologue/epilogue generation.
Ah, this code is generated only then, I see n
> Because you cannot during reload, or another reason? We always use LRA
> on powerpc nowadays, and LRA can deal with this.
Because you cannot during prologue/epilogue generation.
> Only the first hunk (rs6000.md) applies, the rest is ignored (there is a
> blank line here instead of a diff heade
On Fri, Jun 02, 2017 at 10:27:33AM +0200, Eric Botcazou wrote:
> > Could you make the expander handle it, instead? It's as simple as (after
> > the double-reg thing) add "if operands[1] is reg 0, force_reg operands[2]".
> > I'll do it if you prefer.
>
> Probably, because I'm not sure how this can
> Could you make the expander handle it, instead? It's as simple as (after
> the double-reg thing) add "if operands[1] is reg 0, force_reg operands[2]".
> I'll do it if you prefer.
Probably, because I'm not sure how this can work, as you cannot create new
pseudos here.
> [ the patch is broken h
Hi!
[ please cc: me and David on rs6000 patches ]
On Wed, May 24, 2017 at 09:51:46AM +0200, Eric Botcazou wrote:
> this fixes an internal error with -fstack-limit-register and large frames:
>
> eric@polaris:~/build/gcc/powerpc-linux> gcc/xgcc -Bgcc -S stack-limit-1.c -
> fstack-limit-register=r2
Hi,
this fixes an internal error with -fstack-limit-register and large frames:
eric@polaris:~/build/gcc/powerpc-linux> gcc/xgcc -Bgcc -S stack-limit-1.c -
fstack-limit-register=r2
stack-limit-1.c: In function 'foo':
stack-limit-1.c:9:1: error: insn does not satisfy its constraints:
}
^
(insn 21
