public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "toralf.foerster at gmx dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug preprocessor/54694] internal compiler error: in dwarf2out_frame_debug_expr, at dwarf2out.c:2387 Date: Tue, 25 Sep 2012 15:27:00 -0000 [thread overview] Message-ID: <bug-54694-4-y8KyH6tjCO@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54694-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54694 --- Comment #2 from Toralf Förster <toralf.foerster at gmx dot de> 2012-09-25 15:26:25 UTC --- Created attachment 28271 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=28271 cc -E n22 ~ # gcc -v Using built-in specs. COLLECT_GCC=/usr/i686-pc-linux-gnu/gcc-bin/4.6.3/gcc COLLECT_LTO_WRAPPER=/usr/libexec/gcc/i686-pc-linux-gnu/4.6.3/lto-wrapper Target: i686-pc-linux-gnu Configured with: /var/tmp/portage/sys-devel/gcc-4.6.3/work/gcc-4.6.3/configure --prefix=/usr --bindir=/usr/i686-pc-linux-gnu/gcc-bin/4.6.3 --includedir=/usr/lib/gcc/i686-pc-linux-gnu/4.6.3/include --datadir=/usr/share/gcc-data/i686-pc-linux-gnu/4.6.3 --mandir=/usr/share/gcc-data/i686-pc-linux-gnu/4.6.3/man --infodir=/usr/share/gcc-data/i686-pc-linux-gnu/4.6.3/info --with-gxx-include-dir=/usr/lib/gcc/i686-pc-linux-gnu/4.6.3/include/g++-v4 --host=i686-pc-linux-gnu --build=i686-pc-linux-gnu --disable-altivec --disable-fixed-point --without-ppl --without-cloog --enable-lto --enable-nls --without-included-gettext --with-system-zlib --enable-obsolete --disable-werror --enable-secureplt --disable-multilib --enable-libmudflap --disable-libssp --enable-libgomp --with-python-dir=/share/gcc-data/i686-pc-linux-gnu/4.6.3/python --enable-checking=release --disable-libgcj --with-arch=i686 --enable-languages=c,c++,fortran --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu --enable-targets=all --with-bugurl=http://bugs.gentoo.org/ --with-pkgversion='Gentoo 4.6.3 p1.6, pie-0.5.2' Thread model: posix gcc version 4.6.3 (Gentoo 4.6.3 p1.6, pie-0.5.2) n
next prev parent reply other threads:[~2012-09-25 15:27 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-09-24 21:10 [Bug preprocessor/54694] New: " toralf.foerster at gmx dot de 2012-09-25 7:34 ` [Bug preprocessor/54694] " rguenth at gcc dot gnu.org 2012-09-25 15:27 ` toralf.foerster at gmx dot de [this message] 2012-09-26 9:10 ` rguenth at gcc dot gnu.org 2012-09-26 17:19 ` toralf.foerster at gmx dot de 2012-09-26 17:59 ` markus at trippelsdorf dot de 2013-01-03 19:35 ` toralf.foerster at gmx dot de 2013-11-16 21:46 ` valentin.ilie at gmail dot com 2013-11-28 11:45 ` octoploid at yandex dot com 2013-11-28 12:08 ` [Bug debug/54694] [4.7/4.8/4.9 Regression] " Joost.VandeVondele at mat dot ethz.ch 2013-11-28 12:15 ` hjl.tools at gmail dot com 2013-11-28 12:17 ` hjl.tools at gmail dot com 2013-12-19 15:19 ` rguenth at gcc dot gnu.org 2014-01-10 19:17 ` ubizjak at gmail dot com 2014-01-10 19:26 ` hjl.tools at gmail dot com 2014-01-13 19:32 ` rth at gcc dot gnu.org 2014-01-13 19:42 ` toralf.foerster at gmx dot de 2014-01-15 21:41 ` rth at gcc dot gnu.org 2014-01-15 21:47 ` [Bug debug/54694] [4.7/4.8 " rth at gcc dot gnu.org 2014-01-16 16:24 ` rth at gcc dot gnu.org 2014-01-16 16:34 ` rth at gcc dot gnu.org 2014-01-16 16:35 ` rth at gcc dot gnu.org 2014-01-16 19:16 ` jakub at gcc dot gnu.org 2014-01-16 19:21 ` jakub at gcc dot gnu.org 2014-01-16 19:22 ` jakub at gcc dot gnu.org 2015-09-05 2:49 ` gang.chen.5i5j 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-54694-4-y8KyH6tjCO@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).