public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "t.keck at online dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/65721] New: Internal compiler error segmentation fault Date: Thu, 09 Apr 2015 16:42:00 -0000 [thread overview] Message-ID: <bug-65721-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65721 Bug ID: 65721 Summary: Internal compiler error segmentation fault Product: gcc Version: 4.8.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: t.keck at online dot de Following code produces a segmentation fault with gcc 4.8.2. gcc 4.7.2 and 4.6.3 reject the code (which is probably invalid c++), without segmentation code. tkeck@ekplx12:~$ cat test.cpp template<typename T> class A { public: typedef T D; }; template<typename X> class B : public A<X> { using typename B::D; // Triggers segfault and probably invalid C++ //using typename A<X>::D; // Works fine and probably valid C++ public: D echo(D x) { return x; } }; int main() { B<int> b; } tkeck@ekplx12:~$ g++ test.cpp g++: internal compiler error: Segmentation fault (program cc1plus) Please submit a full bug report, with preprocessed source if appropriate. See <file:///usr/share/doc/gcc-4.8/README.Bugs> for instructions. tkeck@ekplx12:~$ g++ -v Using built-in specs. COLLECT_GCC=g++ COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.8/lto-wrapper Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 4.8.2-19ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-4.8/README.Bugs --enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.8 --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.8 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object --disable-libmudflap --enable-plugin --with-system-zlib --disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.8-amd64/jre --enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.8-amd64 --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-4.8-amd64 --with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --enable-objc-gc --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
next reply other threads:[~2015-04-09 16:42 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-04-09 16:42 t.keck at online dot de [this message] 2015-04-09 17:22 ` [Bug c++/65721] [4.8/4.9/5 Regression] " jakub at gcc dot gnu.org 2015-04-10 7:43 ` rguenth at gcc dot gnu.org 2015-04-10 9:47 ` mpolacek at gcc dot gnu.org 2015-04-11 14:42 ` jason at gcc dot gnu.org 2015-04-14 15:30 ` [Bug c++/65721] [4.8/4.9/5/6 " jason at gcc dot gnu.org 2015-04-22 20:53 ` jason at gcc dot gnu.org 2015-04-23 13:20 ` jason at gcc dot gnu.org 2015-04-23 13:21 ` jason at gcc dot gnu.org 2015-04-23 13:24 ` 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-65721-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).