avr-gcc-list
[Top][All Lists]
Advanced

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

Re: [avr-gcc-list] Trunk broken for AVR Target?


From: Boyapati, Anitha
Subject: Re: [avr-gcc-list] Trunk broken for AVR Target?
Date: Thu, 9 Jun 2011 02:28:31 +0800


>>
>>>
>>>
>>> Further probing shows that dwarf-2 information generation is affected.
>>>
>>> --------------------------------------------------------------
>>> configure:3056: /home/anitha/gcc-4.7-20110604/objdir/./gcc/xgcc -
>>> B/home/anitha/gcc-4.7-20110604/objdir/./gcc/ -B/usr/local/avr/bin/ -
>>> B/usr/local/avr/lib/ -isystem /usr/local/avr/include -isystem
>>> /usr/local/avr/sys-include    -o conftest -g -O2   conftest.c  >&5
>>> conftest.c: In function 'main':
>>> conftest.c:16:1: internal compiler error: in
>>> compute_frame_pointer_to_fb_displacement, at dwarf2out.c:18342
>>>
>>> --------------------------------------------------------------
>>>
>>>
>>> I have done some more analysis on the origin of this error, but before
>>> that I think it is a good idea if someone can confirm that the build is
>>> broken.
>>
>>There is already a bug reported in the GCC Bugzilla about DWARF2 not
>>working for the AVR, specifically for 4.6.* and 4.7/trunk. Please double
>>check that you're running into the same bug. No, this bug is not fixed
>yet.
>
>I have followed the below conversation. But the error I get is different.
>Moreover the bug is reported as fixed.
>
>http://lists.nongnu.org/archive/html/avr-gcc-list/2011-04/msg00002.html
>
>
>
>The current build error which I have reported is most likely because of
>http://gcc.gnu.org/viewcvs?diff_format=h&view=revision&revision=171295
>http://gcc.gnu.org/viewcvs?diff_format=h&view=revision&revision=171296
>
>
>(If I apply these patches individually to gcc-4.6.0 release sources, I get
>same error). I am a little confused here because higher revisions (>171295)
>are reported to have built fine.
>

OK. I have put some threads together and it starts making some sense to me. The 
trunk revisions that were reported to have built fine do not use --with-dwarf2 
option during cross-compilation. Hence they work.


I think I must have hit this bug:

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48459

Referring to comment 1, how come avr-gcc got built in the first place? It dies 
compiling libgcc.c...!


Anitha



reply via email to

[Prev in Thread] Current Thread [Next in Thread]