public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dirtyepic at gentoo dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/46734] New: ICE in create_tmp_var, at gimplify.c:505 Date: Wed, 01 Dec 2010 01:00:00 -0000 [thread overview] Message-ID: <bug-46734-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46734 Summary: ICE in create_tmp_var, at gimplify.c:505 Product: gcc Version: 4.5.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: other AssignedTo: unassigned@gcc.gnu.org ReportedBy: dirtyepic@gentoo.org Created attachment 22585 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=22585 segmentAnchorPluckerFeature.i.bz2 Unfortunately the preprocessed source is from boost and huge. I'm trying to reduce it. Both 4.5.1 and current 4.5 branch svn fail. 4.4.5 works. $ g++ -O2 -m32 -c segmentAnchorPluckerFeature.i In file included from /mnt/data/LAAS/Libs/jafar/modules/jmath/include/jmath/ublasExtra.hpp:12:0, from /mnt/data/LAAS/Libs/jafar/modules/slam/src/segmentAnchorPluckerFeature.cpp:6: /usr/include/boost/numeric/ublas/vector_proxy.hpp: In function 'boost::numeric::ublas::vector_range<V> boost::numeric::ublas::vector_range<V>::project(const boost::numeric::ublas::vector_range<V>::range_type&) const [with V = boost::numeric::ublas::vector<double>, boost::numeric::ublas::vector_range<V>::range_type = boost::numeric::ublas::basic_range<>, typename A::difference_type = int, typename A::size_type = unsigned int]': /usr/include/boost/numeric/ublas/vector_proxy.hpp:62:58: internal compiler error: in create_tmp_var, at gimplify.c:505 $ g++ -v Using built-in specs. COLLECT_GCC=/usr/x86_64-unknown-linux-gnu/gcc-bin/4.5.2-pre9999/g++ COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-unknown-linux-gnu/4.5.2-pre9999/lto-wrapper Target: x86_64-unknown-linux-gnu Configured with: /var/tmp/portage/sys-devel/gcc-4.5.2_pre9999/work/gcc-4.5.2-9999/configure --prefix=/usr --bindir=/usr/x86_64-unknown-linux-gnu/gcc-bin/4.5.2-pre9999 --includedir=/usr/lib/gcc/x86_64-unknown-linux-gnu/4.5.2-pre9999/include --datadir=/usr/share/gcc-data/x86_64-unknown-linux-gnu/4.5.2-pre9999 --mandir=/usr/share/gcc-data/x86_64-unknown-linux-gnu/4.5.2-pre9999/man --infodir=/usr/share/gcc-data/x86_64-unknown-linux-gnu/4.5.2-pre9999/info --with-gxx-include-dir=/usr/lib/gcc/x86_64-unknown-linux-gnu/4.5.2-pre9999/include/g++-v4 --host=x86_64-unknown-linux-gnu --build=x86_64-unknown-linux-gnu --disable-altivec --disable-fixed-point --with-ppl --with-cloog --enable-lto --disable-nls --with-system-zlib --disable-werror --enable-secureplt --enable-multilib --disable-libmudflap --disable-libssp --enable-libgomp --enable-cld --with-python-dir=/share/gcc-data/x86_64-unknown-linux-gnu/4.5.2-pre9999/python --enable-checking=release --disable-libgcj --enable-languages=c,c++ --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu --with-bugurl=http://bugs.gentoo.org/ --with-pkgversion='Gentoo SVN' Thread model: posix gcc version 4.5.2-pre9999 20101130 (prerelease) rev. 167289 (Gentoo SVN)
next reply other threads:[~2010-12-01 1:00 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-12-01 1:00 dirtyepic at gentoo dot org [this message] 2010-12-01 13:59 ` [Bug middle-end/46734] [4.5 Regression] " rguenth at gcc dot gnu.org 2010-12-02 0:29 ` dirtyepic at gentoo dot org 2010-12-05 11:58 ` rguenth at gcc dot gnu.org 2010-12-05 16:47 ` hjl.tools at gmail dot com 2010-12-07 13:29 ` jamborm at gcc dot gnu.org 2010-12-07 13:32 ` jamborm at gcc dot gnu.org 2010-12-07 13:35 ` jamborm at gcc dot gnu.org 2010-12-09 15:11 ` jamborm at gcc dot gnu.org 2010-12-16 13:20 ` rguenth at gcc dot gnu.org 2010-12-21 11:06 ` jamborm at gcc dot gnu.org 2010-12-21 11:08 ` jamborm 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-46734-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: 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).