public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/54632] [4.8 Regression] not supported in LTO streams : tree code '�F ��D�� `
Date: Thu, 20 Sep 2012 11:32:00 -0000 [thread overview]
Message-ID: <bug-54632-4-9AwwAorNma@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54632-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54632
Richard Guenther <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dehao at gcc dot gnu.org
Target Milestone|--- |4.8.0
Summary|not supported in LTO |[4.8 Regression] not
|streams : tree code '�F |supported in LTO streams :
|��D�� ` |tree code '�F ��D�� `
--- Comment #2 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-09-20 11:31:49 UTC ---
It's outputting a garbage collected tree. Suspect it was a BLOCK.
next prev parent reply other threads:[~2012-09-20 11:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-20 7:55 [Bug lto/54632] New: " dimhen at gmail dot com
2012-09-20 7:57 ` [Bug lto/54632] " dimhen at gmail dot com
2012-09-20 11:32 ` rguenth at gcc dot gnu.org [this message]
2012-09-23 9:22 ` [Bug lto/54632] [4.8 Regression] " dimhen at gmail dot com
2012-09-23 9:33 ` dimhen at gmail dot com
2012-09-23 10:50 ` zsojka at seznam dot cz
2012-09-23 10:55 ` dimhen at gmail dot com
2012-09-23 13:06 ` markus at trippelsdorf dot de
2012-09-24 9:26 ` rguenth at gcc dot gnu.org
2012-09-24 9:39 ` zsojka at seznam dot cz
2012-09-24 9:46 ` dimhen at gmail dot com
2012-09-24 12:28 ` markus at trippelsdorf dot de
2012-09-24 12:43 ` rguenth at gcc dot gnu.org
2012-09-24 15:03 ` rguenth at gcc dot gnu.org
2012-09-24 15:03 ` rguenth 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-54632-4-9AwwAorNma@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).