public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marbacz at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/51992] New: internal compiler error: tree code ‘target_expr’ is not supported in LTO streams
Date: Wed, 25 Jan 2012 10:27:00 -0000	[thread overview]
Message-ID: <bug-51992-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51992

             Bug #: 51992
           Summary: internal compiler error: tree code ‘target_expr’ is
                    not supported in LTO streams
    Classification: Unclassified
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Severity: major
          Priority: P3
         Component: lto
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: marbacz@gmail.com


Created attachment 26456
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26456
Reduced test case.

Using GCC from SVN (183488) I get an ICE while compiling kdelibs with -flto:

~ # g++ -flto -c ksharedconfig.cpp
ksharedconfig.cpp:50:1: internal compiler error: tree code ‘target_expr’ is not
supported in LTO streams
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.


~ # gcc -v
Using built-in specs.
COLLECT_GCC=/usr/x86_64-pc-linux-gnu/gcc-bin/4.7.0-svn-183488-20120124/gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-pc-linux-gnu/4.7.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ../gcc-trunk/configure --prefix=/usr
--bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/4.7.0-svn-183488-20120124
--includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.0-svn-183488-20120124/include
--datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.7.0-svn-183488-20120124
--mandir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.7.0-svn-183488-20120124/man
--infodir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.7.0-svn-183488-20120124/info
--with-gxx-include-dir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.0-svn-183488-20120124/include/g++-v4
--host=x86_64-pc-linux-gnu --build=x86_64-pc-linux-gnu --disable-altivec
--disable-fixed-point --with-ppl --with-cloog --disable-ppl-version-check
--with-cloog-include=/usr/include/cloog-ppl --enable-lto --enable-nls
--without-included-gettext --with-system-zlib --disable-werror
--enable-secureplt --disable-multilib --enable-libmudflap --enable-libssp
--enable-libgomp
--with-python-dir=/share/gcc-data/x86_64-pc-linux-gnu/4.7.0-svn-183488-20120124/python
--enable-checking=assert,fold,gc,misc,rtlflag,runtime,tree --disable-libgcj
--disable-libquadmath --enable-languages=c,c++ --enable-shared
--enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu
--enable-targets=all --with-pkgversion='svn 183488-20120124'
--enable-build-with-cxx
Thread model: posix
gcc version 4.7.0 20120124 (experimental) (svn 183488-20120124)


             reply	other threads:[~2012-01-25 10:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-25 10:27 marbacz at gmail dot com [this message]
2012-01-25 10:30 ` [Bug c++/51992] [4.7 Regression] " rguenth at gcc dot gnu.org
2012-01-25 14:28 ` jason at gcc dot gnu.org
2012-01-25 17:42 ` jason at gcc dot gnu.org
2012-01-25 17:42 ` jason 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-51992-4@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).