public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/51916] FAIL: gcc.dg/lto/trans-mem-3 c_lto_trans-mem-3_0.o-c_lto_trans-mem-3_1.o link, -flto (internal compiler error)
Date: Sat, 21 Jan 2012 00:01:00 -0000 [thread overview]
Message-ID: <bug-51916-4-GzT3dRubay@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51916-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51916
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |iains at gcc dot gnu.org
--- Comment #6 from Dominique d'Humieres <dominiq at lps dot ens.fr> 2012-01-20 22:46:47 UTC ---
> From the Debugging GCC wiki (http://gcc.gnu.org/wiki/DebuggingGCC):
>
> To build a debuggable compiler, configure the compiler normally and then
>
> make STAGE1_CFLAGS="-g -O0" all-stage1
With that I get
Breakpoint 1, streamer_get_builtin_tree (ib=find_location_expression: Corrupted
DWARF expression.
) at ../../_clean/gcc/tree-streamer-in.c:1067
and 'Corrupted DWARF expression' for every attempt to print something. I am
lost!-(
next prev parent reply other threads:[~2012-01-20 22:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-20 13:25 [Bug lto/51916] New: " dominiq at lps dot ens.fr
2012-01-20 15:52 ` [Bug lto/51916] " aldyh at gcc dot gnu.org
2012-01-20 16:26 ` dominiq at lps dot ens.fr
2012-01-20 16:50 ` aldyh at redhat dot com
2012-01-20 19:18 ` dominiq at lps dot ens.fr
2012-01-20 20:08 ` aldyh at redhat dot com
2012-01-21 0:01 ` dominiq at lps dot ens.fr [this message]
2012-01-21 0:03 ` patrick.marlier at gmail dot com
2012-01-21 10:56 ` iains at gcc dot gnu.org
2012-01-21 11:22 ` iains at gcc dot gnu.org
2012-01-23 10:24 ` rguenth at gcc dot gnu.org
2012-01-23 10:28 ` dominiq at lps dot ens.fr
2012-01-23 14:11 ` aldyh at gcc dot gnu.org
2012-01-23 14:44 ` aldyh 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-51916-4-GzT3dRubay@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).