public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "chihin.ko at oracle dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/54774] [4.4.4, 4.5, 4.6, 4.7] insufficient debug info for strong typed enum Date: Thu, 06 Dec 2012 19:58:00 -0000 [thread overview] Message-ID: <bug-54774-4-jfNA3zk4KQ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54774-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54774 chihin ko <chihin.ko at oracle dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|insufficient debug info for |[4.4.4, 4.5, 4.6, 4.7] |strong typed enum |insufficient debug info for | |strong typed enum --- Comment #3 from chihin ko <chihin.ko at oracle dot com> 2012-12-06 19:57:46 UTC --- This problem can trace back from gcc 4.4.4.
next prev parent reply other threads:[~2012-12-06 19:58 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-02 0:39 [Bug debug/54774] New: " chihin.ko at oracle dot com 2012-10-02 10:53 ` [Bug debug/54774] " jakub at gcc dot gnu.org 2012-11-23 14:50 ` paolo.carlini at oracle dot com 2012-12-06 19:58 ` chihin.ko at oracle dot com [this message] 2012-12-06 20:39 ` jakub at gcc dot gnu.org 2012-12-07 0:11 ` paolo.carlini at oracle dot com 2014-03-24 14:32 ` mark at gcc dot gnu.org 2014-06-25 18:55 ` tromey 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-54774-4-jfNA3zk4KQ@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).