public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/48773] Dataflow and REG_DEAD notes Date: Thu, 28 Apr 2011 20:54:00 -0000 [thread overview] Message-ID: <bug-48773-4-Tp42nQKlth@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-48773-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48773 Eric Botcazou <ebotcazou at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2011.04.28 20:48:36 CC| |ebotcazou at gcc dot | |gnu.org Ever Confirmed|0 |1 Severity|major |normal --- Comment #5 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2011-04-28 20:48:36 UTC --- This is a known issue introduced by the DF merge. I think that the current state of affairs is that the passes consuming REG_DEAD/REG_UNUSED notes have to invoke df_note_add_problem on entry.
next prev parent reply other threads:[~2011-04-28 20:54 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-04-26 15:00 [Bug rtl-optimization/48773] New: " mfortune at gmail dot com 2011-04-28 11:59 ` [Bug rtl-optimization/48773] " mfortune at gmail dot com 2011-04-28 12:02 ` mfortune at gmail dot com 2011-04-28 12:02 ` mfortune at gmail dot com 2011-04-28 12:05 ` mfortune at gmail dot com 2011-04-28 20:54 ` ebotcazou at gcc dot gnu.org [this message] 2011-05-04 16:25 ` mfortune at gmail dot com 2011-05-04 16:42 ` ebotcazou at gcc dot gnu.org 2011-05-04 16:59 ` froydnj at codesourcery dot com 2013-12-24 23:46 ` steven 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-48773-4-Tp42nQKlth@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).