public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wilbur dot harvey at spirentcom dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/26504] New: compute_frame_pointer_to_cfa_displacement error for avr target
Date: Wed, 01 Mar 2006 02:25:00 -0000 [thread overview]
Message-ID: <bug-26504-12286@http.gcc.gnu.org/bugzilla/> (raw)
When trying to compile gcc4.10 for the AVR processor under Ubuntu Dapper
(gcc4.0.3) I get this error:
../../gcc/libgcc2.c: In function '__fixunssfsi':
../../gcc/libgcc2.c:1499: internal compiler error: in
compute_frame_pointer_to_cfa_displacement, at dwarf2out.c:10445
Please submit a full bug report,
Config arguments
wilbur.harvey@shuttle1:~/avrtools/gcc-4.1.0/obj-avr$ ../configure
--prefix=$PREFIX --target=avr --enable-languages=c,c++ --disable-nls
--with-dwarf2
I previously compiled the binutils2.16 under the same environment without any
problems.
--
Summary: compute_frame_pointer_to_cfa_displacement error for avr
target
Product: gcc
Version: 4.1.0
Status: UNCONFIRMED
Severity: critical
Priority: P3
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: wilbur dot harvey at spirentcom dot com
GCC build triplet: ???
GCC host triplet: Ubuntu Dapper gcc4.0.3
GCC target triplet: AVR
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26504
next reply other threads:[~2006-03-01 2:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-01 2:25 wilbur dot harvey at spirentcom dot com [this message]
2006-03-01 2:30 ` [Bug target/26504] " pinskia at gcc dot gnu dot org
2006-03-01 2:31 ` pinskia at gcc dot gnu dot org
2006-03-02 12:29 ` [Bug target/26504] compute_frame_pointer_to_cfa_displacement error for avr target with --with-dwarf2 pinskia at gcc dot gnu dot org
2006-03-02 16:04 ` bjkeen at super dot org
2006-03-02 16:06 ` bjkeen at super dot org
2006-03-02 20:01 ` wilbur dot harvey at spirentcom dot com
2006-03-03 2:17 ` pinskia at gcc dot gnu dot org
2006-03-21 16:08 ` yannick dot podgorski at kuantic dot com
2006-04-05 20:11 ` bjkeen at super dot org
2006-07-05 17:32 ` pinskia at gcc dot gnu dot org
2006-07-09 21:34 ` andreas at fink dot org
2006-08-28 15:38 ` clemens dot koller at anagramm dot de
2006-09-03 5:33 ` [Bug target/26504] [4.1/4.2 Regression] " pinskia at gcc dot gnu dot org
2006-09-07 1:14 ` mmitchel at gcc dot gnu dot org
2006-09-14 21:11 ` aesok at gcc dot gnu dot org
2006-09-14 21:19 ` aesok at gcc dot gnu dot org
2006-09-14 21:39 ` aesok at gcc dot gnu dot org
2006-10-10 16:27 ` pinskia at gcc dot gnu dot org
2006-10-10 22:18 ` aesok at gcc dot gnu dot org
2006-11-17 1:41 ` pinskia at gcc dot gnu dot org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-26504-12286@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).