This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: internal compiler error: in reload_combine_note_use, at postreload.c:1093
- From: daniel tian <daniel dot xntian at gmail dot com>
- To: Dave Korn <dave dot korn dot cygwin at googlemail dot com>
- Cc: gcc at gcc dot gnu dot org, Ian Lance Taylor <iant at google dot com>, yxun lan <dennis dot yxun at gmail dot com>
- Date: Thu, 14 May 2009 11:54:17 +0800
- Subject: Re: internal compiler error: in reload_combine_note_use, at postreload.c:1093
- References: <121fadb80905130255h47064421we320de6c54dabed2@mail.gmail.com> <4A0AB284.3040202@gmail.com>
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 places.
Anything I missed?
2009/5/13 Dave Korn <dave.korn.cygwin@googlemail.com>:
> 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 mean
>> the reload register allocation failed? ?What I know is that there is
>> no pseudo register used after reload completed (Is this right?).
>
> ?Yes, this is correct.
>
>> Can anyone give me some advice?
>
> ?It is most likely one of the expanders or other patterns in your MD file is
> unconditionally calling a function such as force_reg() without checking the
> reload_completed / reload_in_progress flags. ?If this pattern gets invoked
> post-reload, that will allocate a pseudo and then fail later.
>
> ? ?cheers,
> ? ? ?DaveK
>
>
>