Re: Bad Register Number for libgcc

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 3/10/13, Jens Mehler <jens.mehler@xxxxxxxxxx> wrote:
>
> I have ported the GCC-4.5.3 for a 32-bit CPU.
> Building GCC works like charm, even assembling several tests I wrote
> myself works.
> After porting the Gnu-Binutils I took my first approach of building libgcc.
> Poorly it runs into an error.
>
> ../../../gcc-4.5.3/libgcc/../gcc/libgcc2.c: In function '__powidf2':
> ../../../gcc-4.5.3/libgcc/../gcc/libgcc2.c:1739:1: internal compiler
> error: in use_type, at var-tracking.c:4903
>
> On var-tracking.c line 4903:
> gcc_assert (REGNO (loc) < FIRST_PSEUDO_REGISTER);
> loc is an RTX.
>
> Can someone please give me pointer where the problem might be.
> If additional information is I will provide them.

Well, there is something wrong with your port.  It's pretty hard to
say what it is, though.  The var tracking pass runs after the register
allocation pass, which means that at that point in the compilation
there should not be any pseudo-registers, only hard registers.
Somehow you have a pseudo-register left.  I don't know how.

Ian


[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux