"Bingfeng Mei" writes:
> In our porting, "movm" is implemented as define_expand. Register move and
> memory
> move are implmeneted in different define_insn. Register move pattern has no
> "m" alternative, and thus causes the "asm operand requires impossible reload".
> I should merge these two pa
text to avoid
future confusion.
Cheers,
Bingfeng Mei
Broadcom UK
> -Original Message-
> From: Ian Lance Taylor [mailto:i...@google.com]
> Sent: 01 May 2009 15:32
> To: Bingfeng Mei
> Cc: gcc@gcc.gnu.org; bernd.schm...@analog.com; weig...@de.ibm.com
> Subject: Re: Re
"Bingfeng Mei" writes:
> Actually, they do contain references to pseudo-registers. Only in following
> code (reload function in reload1.c, after the reload_as_needed function
> that emits error message), pseudo registers are replaced with requivalent
> memory operands.
Yes, but the insns generat
> -Original Message-
> From: Ian Lance Taylor [mailto:i...@google.com]
> Sent: 01 May 2009 15:32
> To: Bingfeng Mei
> Cc: gcc@gcc.gnu.org; bernd.schm...@analog.com; weig...@de.ibm.com
> Subject: Re: Reload problem: asm operand requires impossible reload
>
>
"Bingfeng Mei" writes:
> I experienced "asm operand requires impossible reload" error in our private
> porting.
> After digging into the reloading pass, I found something a bit fishy.
>
> The error message is produced in reload_as_needed function (reload1.c)
>
> ...
> /* If this wa
Hello,
I experienced "asm operand requires impossible reload" error in our private
porting.
After digging into the reloading pass, I found something a bit fishy.
The error message is produced in reload_as_needed function (reload1.c)
...
/* If this was an ASM, make sure that all
