public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dimhen at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/54794] [4.8 regression] tree code '�F Hc���' is not supported in LTO streams Date: Wed, 03 Oct 2012 14:04:00 -0000 [thread overview] Message-ID: <bug-54794-4-DR6e1iHv1m@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54794-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54794 --- Comment #2 from Dmitry G. Dyachenko <dimhen at gmail dot com> 2012-10-03 14:04:06 UTC --- i have 23 src-files hence 23 ii-files with about 50Mb code if i remove any file from build then err not triggered (at beginning there were 29 files) i'll run creduce tonight. Oh, cycle throw 23 files :)
next prev parent reply other threads:[~2012-10-03 14:04 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-03 13:38 [Bug lto/54794] New: " dimhen at gmail dot com 2012-10-03 13:47 ` [Bug lto/54794] " markus at trippelsdorf dot de 2012-10-03 14:04 ` dimhen at gmail dot com [this message] 2012-10-04 12:16 ` rguenth at gcc dot gnu.org 2012-10-04 15:34 ` hjl.tools at gmail dot com 2012-10-07 10:26 ` dimhen at gmail dot com 2012-10-10 15:12 ` dimhen at gmail dot com 2012-10-10 15:14 ` dimhen at gmail dot com
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-54794-4-DR6e1iHv1m@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: linkBe 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).