public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tnorth at fedoraproject dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/46898] libgcc build failure on lm32-elf
Date: Tue, 12 Apr 2011 19:07:00 -0000 [thread overview]
Message-ID: <bug-46898-4-iqVMfKEnX4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46898-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46898
Thibault North <tnorth at fedoraproject dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tnorth at fedoraproject dot
| |org
--- Comment #15 from Thibault North <tnorth at fedoraproject dot org> 2011-04-12 19:07:04 UTC ---
Same problem with the AVR arch, using the same testcase:
avr-gcc-4.5.2: OK
avr-gcc-4.6.0: avr-gcc -gdwarf-2 foo.c
foo.c:1:0: internal compiler error: in dwarf2out_frame_init, at
dwarf2out.c:4260
Please submit a full bug report,
with preprocessed source if appropriate.
$ avr-gcc -v
Using built-in specs.
COLLECT_GCC=/usr/bin/avr-gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/avr/4.6.0/lto-wrapper
Target: avr
Configured with: ../gcc-4.6.0/configure --prefix=/usr --mandir=/usr/share/man
--infodir=/usr/share/info --target=avr --enable-languages=c,c++ --disable-nls
--disable-libssp --with-system-zlib --enable-version-specific-runtime-libs
--with-pkgversion='Fedora 4.6.0-1.fc14'
--with-bugurl=https://bugzilla.redhat.com/
Thread model: single
gcc version 4.6.0 (Fedora 4.6.0-1.fc14)
next prev parent reply other threads:[~2011-04-12 19:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-12 0:33 [Bug target/46898] New: " monaka@monami-software.com
2010-12-12 3:26 ` [Bug target/46898] " monaka@monami-software.com
2010-12-12 3:37 ` monaka@monami-software.com
2011-01-25 5:46 ` joel at gcc dot gnu.org
2011-01-25 15:09 ` joel at gcc dot gnu.org
2011-02-01 21:25 ` lekernel at gcc dot gnu.org
2011-02-01 21:37 ` joel at gcc dot gnu.org
2011-02-01 22:00 ` lekernel at gcc dot gnu.org
2011-02-06 22:07 ` lekernel at gcc dot gnu.org
2011-02-25 16:56 ` lekernel at gcc dot gnu.org
2011-02-25 17:39 ` joel at gcc dot gnu.org
2011-02-25 19:09 ` lekernel at gcc dot gnu.org
2011-02-25 19:10 ` lekernel at gcc dot gnu.org
2011-02-25 21:17 ` lekernel at gcc dot gnu.org
2011-02-25 21:23 ` lekernel at gcc dot gnu.org
2011-04-12 19:07 ` tnorth at fedoraproject dot org [this message]
2011-07-24 22:32 ` eric.weddington at atmel dot com
2014-03-02 19:59 ` jbeniston at gcc dot gnu.org
2014-03-02 21:55 ` lekernel at gcc dot gnu.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-46898-4-iqVMfKEnX4@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).