public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "phorgan1 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/40705] New: Using -ggdb flag cause internal Date: Thu, 09 Jul 2009 21:32:00 -0000 [thread overview] Message-ID: <bug-40705-16244@http.gcc.gnu.org/bugzilla/> (raw) The following code compiles cleanly without the -ggdb flag, i.e. using: g++ -save-temps testit.cpp -o testit but adding the -ggdb flag: g++ -ggdb -save-temps testit.cpp -o testit results in the following error output: testit.cpp:10:1: internal compiler error: in gen_type_die_with_usage, at dwarf2out.c:15108 Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. Exact code compiled from testit.ii: # 1 "testit.cpp" # 1 "<built-in>" # 1 "<command-line>" # 1 "testit.cpp" template <unsigned int n> class foo { public: typedef unsigned char type; }; template<> class foo<1> { typedef enum {} type; }; int main() { } -- Summary: Using -ggdb flag cause internal Product: gcc Version: 4.5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: phorgan1 at gmail dot com GCC build triplet: i686-pc-linux-gnu GCC host triplet: i686-pc-linux-gnu GCC target triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40705
next reply other threads:[~2009-07-09 21:32 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-07-09 21:32 phorgan1 at gmail dot com [this message] 2009-07-09 21:45 ` [Bug c++/40705] Using -ggdb flag cause internal error phorgan1 at gmail dot com 2009-07-10 8:35 ` [Bug debug/40705] [4.5 Regression] ICE in gen_type_die_with_usage, at dwarf2out.c:15117 rguenth at gcc dot gnu dot org 2009-07-10 13:45 ` dodji at gcc dot gnu dot org 2009-07-13 17:41 ` dodji at gcc dot gnu dot org 2009-07-14 15:02 ` dodji at gcc dot gnu dot org 2009-07-14 15:19 ` dodji at gcc dot gnu dot org 2009-07-14 19:37 ` phorgan1 at gmail dot com 2009-07-23 17:52 ` hjl at gcc dot gnu dot 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-40705-16244@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).