public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl at lucon dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/21828] [4.0/4.1 Regression] debug info omitted for uninitialized variables Date: Tue, 05 Jul 2005 16:56:00 -0000 [thread overview] Message-ID: <20050705165646.7776.qmail@sourceware.org> (raw) In-Reply-To: <20050530184504.21828.bonzini@gcc.gnu.org> ------- Additional Comments From hjl at lucon dot org 2005-07-05 16:56 ------- Patches for mainline and 4.0 are posted at http://gcc.gnu.org/ml/gcc-patches/2005-07/msg00270.html I hope they lead to the proper fixes and this critical regression is fixed in 4.0.1. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21828
next prev parent reply other threads:[~2005-07-05 16:56 UTC|newest] Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-05-30 18:49 [Bug debug/21828] New: [4.1 Regression] stabs debug info completely broken? bonzini at gcc dot gnu dot org 2005-05-31 5:38 ` [Bug debug/21828] " dje at gcc dot gnu dot org 2005-05-31 13:15 ` [Bug debug/21828] [4.0/4.1 Regression] debug info omitted for global variables bonzini at gcc dot gnu dot org 2005-06-05 23:48 ` mmitchel at gcc dot gnu dot org 2005-06-05 23:50 ` pinskia at gcc dot gnu dot org 2005-06-06 0:16 ` mark at codesourcery dot com 2005-06-06 0:21 ` mmitchel at gcc dot gnu dot org 2005-06-06 0:47 ` mmitchel at gcc dot gnu dot org 2005-07-04 17:54 ` pinskia at gcc dot gnu dot org 2005-07-04 17:59 ` hjl at lucon dot org 2005-07-04 18:21 ` hjl at lucon dot org 2005-07-04 20:06 ` [Bug debug/21828] [4.0/4.1 Regression] debug info omitted for uninitialized variables hjl at lucon dot org 2005-07-05 6:09 ` hjl at lucon dot org 2005-07-05 16:56 ` hjl at lucon dot org [this message] 2005-07-08 0:46 ` wilson at specifix dot com 2005-07-08 1:44 ` mmitchel at gcc dot gnu dot org 2005-07-08 2:01 ` mark at codesourcery dot com 2005-07-19 23:36 ` dpatel at apple dot com 2005-07-20 12:31 ` jakub at redhat dot com 2005-07-20 14:47 ` mark at codesourcery dot com 2005-07-21 23:26 ` mmitchel at gcc dot gnu dot org 2005-07-22 6:52 ` mark at codesourcery dot com 2005-07-22 7:14 ` mark at codesourcery dot com 2005-07-22 17:43 ` cvs-commit at gcc dot gnu dot org 2005-07-22 17:46 ` [Bug debug/21828] [4.0 " mmitchel at gcc dot gnu dot org 2005-07-22 19:34 ` cvs-commit at gcc dot gnu dot org 2005-07-22 19:48 ` mmitchel at gcc dot gnu dot org 2005-07-22 20:45 ` hjl at lucon dot org 2005-07-22 20:49 ` hjl at lucon dot org 2005-07-22 20:50 ` mark at codesourcery dot com 2005-07-22 20:55 ` hjl at lucon dot org 2005-07-22 21:02 ` mark at codesourcery dot com 2005-07-22 21:10 ` pinskia at gcc dot gnu dot org 2005-07-22 23:31 ` dpatel at apple dot com 2005-07-22 23:48 ` mark at codesourcery dot com
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=20050705165646.7776.qmail@sourceware.org \ --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).