> Shouldn't it be simply the abstract origin for the VAR_DECL? Or be
> not 'lowered'
> here but be a 'proper' PARM_DECL with DECL_VALUE_EXPR? That said,
> how is debug info emitted in the optimize case?
This is a PARM_DECL with DECL_VALUE_EXPR set to the VAR_DECL emitted in the
outermost functi
On Mon, Oct 22, 2012 at 10:04 AM, Eric Botcazou wrote:
> We generate a special PARM_DECL for Out parameters passed by copy at -O0, but
> it doesn't play nice with LTO so this patch removes it when LTO is enabled.
>
> Tested on x86_64-suse-linux, applied on the mainline and 4.7 branch.
Shouldn't i
We generate a special PARM_DECL for Out parameters passed by copy at -O0, but
it doesn't play nice with LTO so this patch removes it when LTO is enabled.
Tested on x86_64-suse-linux, applied on the mainline and 4.7 branch.
2012-10-22 Eric Botcazou
* gcc-interface/decl.c (gnat_to_gnu
