This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Reload problem: asm operand requires impossible reload


"Bingfeng Mei" <bmei@broadcom.com> 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 patterns into one. 
>
> Looking at the descrption of "movm" in internal manual, I found this subtle
> requirement is not documented. Maybe we should add some text to avoid
> future confusion. 

Yes, you are correct in both cases: you must have only one basic move
insn for each mode which must handle all cases, and clearer
documentation about that requirement would be helpful.

Ian


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]