public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mr dot chr dot schmidt at online dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/45201] New: ICE: stack overflow during debug information generation Date: Thu, 05 Aug 2010 21:51:00 -0000 [thread overview] Message-ID: <bug-45201-19064@http.gcc.gnu.org/bugzilla/> (raw) The attached code will lead to a stack overflow if compiled with -std=c++0x and -g . The code compiles fine without -g. gcc-4.5.0 accepts the code just fine as well, even when compiled with -g. -- Summary: ICE: stack overflow during debug information generation Product: gcc Version: 4.5.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: mr dot chr dot schmidt at online dot de GCC host triplet: i686-pc-mingw32 GCC target triplet: i686-pc-mingw32 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45201
next reply other threads:[~2010-08-05 21:51 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-08-05 21:51 mr dot chr dot schmidt at online dot de [this message] 2010-08-05 21:53 ` [Bug c++/45201] " mr dot chr dot schmidt at online dot de 2010-08-05 21:54 ` mr dot chr dot schmidt at online dot de 2010-08-06 10:37 ` rguenth at gcc dot gnu dot org 2010-08-07 19:59 ` [Bug c++/45201] ICE: stack overflow mr dot chr dot schmidt at online dot de 2010-08-07 20:00 ` mr dot chr dot schmidt at online dot de 2010-08-07 20:01 ` mr dot chr dot schmidt at online dot de 2010-08-11 0:16 ` pinskia at gcc dot gnu dot org 2010-08-11 20:00 ` mr dot chr dot schmidt at online dot de 2010-08-11 20:01 ` mr dot chr dot schmidt at online dot de
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-45201-19064@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).