Except if I'm mistaken, force_reg will generally call gen_reg_rtx
which does check for those two flags internally (via
can_create_pseudo_p). So you should not have that error in this case.
I suggest you use a debug_rtx on the operand that's a problem, and
first check if gen_reg_rtx is used to crea
Thank you for your advice.
Yes. I checked the MD file and relative machine.h/.c, there are some
places which call the ''force_reg' unconditionally. I modified the it
in "movm" insn pattern, the error still exists. And I also check the
mips/arm, they also call 'force_reg' unconditional in some plac
daniel tian wrote:
> I have ported gcc4.0.2 to 32bit RISC chip. But internal compiler
> error happened: in reload_combine_note_use, at postreload.c:1093 . I
> tracked the code with insight. error occurred in "CASE REG", when the
> register number is larger than FIRST_PSEUDO_REGISTER. Does this me
I have ported gcc4.0.2 to 32bit RISC chip. But internal compiler
error happened: in reload_combine_note_use, at postreload.c:1093 . I
tracked the code with insight. error occurred in "CASE REG", when the
register number is larger than FIRST_PSEUDO_REGISTER. Does this mean
the reload register allo
