public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "paolo.carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/51722] Options "-g3" or "-ggdb3" or "-g3 -gdwarf-2" and other "-g..level3" - internal compiler error Date: Sun, 01 Jan 2012 11:11:00 -0000 [thread overview] Message-ID: <bug-51722-4-ZWcD9vgmGM@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51722-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51722 Paolo Carlini <paolo.carlini at oracle dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |WAITING Last reconfirmed| |2012-01-01 Ever Confirmed|0 |1 --- Comment #1 from Paolo Carlini <paolo.carlini at oracle dot com> 2012-01-01 11:10:45 UTC --- Please provide all the required information, in particular the preprocessed .ii: http://gcc.gnu.org/bugs/#need
next prev parent reply other threads:[~2012-01-01 11:11 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-12-31 17:31 [Bug c++/51722] New: " ylalym at gmail dot com 2012-01-01 11:11 ` paolo.carlini at oracle dot com [this message] 2012-01-02 10:16 ` [Bug c++/51722] " rguenth at gcc dot gnu.org 2012-01-02 15:06 ` ylalym at gmail dot com 2012-01-02 15:16 ` ylalym at gmail dot com 2012-01-02 18:50 ` ylalym at gmail dot com 2012-01-02 18:58 ` ylalym at gmail dot com 2012-01-03 4:39 ` hp at gcc dot gnu.org 2012-01-03 6:05 ` ylalym at gmail dot com 2012-01-03 6:08 ` ylalym at gmail dot com 2012-01-03 6:17 ` ylalym at gmail dot com 2012-01-03 6:18 ` ylalym at gmail dot com 2012-01-03 9:08 ` [Bug pch/51722] [4.7 Regression] " rguenth at gcc dot gnu.org 2012-01-03 9:55 ` jakub at gcc dot gnu.org 2012-01-03 13:46 ` jakub at gcc dot gnu.org 2012-01-03 13:48 ` jakub 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-51722-4-ZWcD9vgmGM@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).