On Thu, Oct 9, 2014 at 11:39 AM, Eric Botcazou wrote:
>> OK, I guess I can copy-and-paste reload1.c:spill_failure there.
>
> This generates the same error message than reload1.c:spill_failure (modulo the
> class of the spill register, but it's not mentioned in the asm case either).
>
> Tested on x
> OK, I guess I can copy-and-paste reload1.c:spill_failure there.
This generates the same error message than reload1.c:spill_failure (modulo the
class of the spill register, but it's not mentioned in the asm case either).
Tested on x86_64-suse-linux, OK for the mainline?
2014-10-09 Eric Botca
> The docs on the asm_p flags say there is sth wrong with the asm constraints
> so maybe better do
>
> if (!asm_p)
>error_at (loc, "");
>
> with an appropriate message and location?
OK, I guess I can copy-and-paste reload1.c:spill_failure there.
--
Eric Botcazou
On Mon, Oct 6, 2014 at 12:02 PM, Eric Botcazou wrote:
> Hi,
>
> we have run into a case on the ARM where LRA silently generates wrong code in
> release mode, while reload (-mno-lra) would stop with the usual spill failure.
>
> Tested on x86_64-suse-linux, OK for the mainline?
The docs on the asm_
Hi,
we have run into a case on the ARM where LRA silently generates wrong code in
release mode, while reload (-mno-lra) would stop with the usual spill failure.
Tested on x86_64-suse-linux, OK for the mainline?
2014-10-06 Eric Botcazou
* lra-assigns.c (assign_by_spills): Turn lra_a
