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 target/64331] regcprop propagates registers noted as REG_DEAD
Date: Wed, 17 Dec 2014 15:12:00 -0000	[thread overview]
Message-ID: <bug-64331-4-3WS7pFTkbV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64331-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64331

--- Comment #5 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> Is it just REG_USED/REG_DEAD notes, or is register liveliness
> (df_regs_ever_live_p etc..) also not guaranteed to be up to date?

These REG_UNUSED/REG_DEAD notes are special because they are not maintained
incrementally by the DF framework, i.e. the insn manipulation routines don't
cause them to be updated, so they are really valid only just after they are
recomputed.  The rest of the liveness info is updated incrementally (if DF is
asked to).


  parent reply	other threads:[~2014-12-17 15:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-16 13:07 [Bug rtl-optimization/64331] New: " senthil_kumar.selvaraj at atmel dot com
2014-12-16 13:08 ` [Bug rtl-optimization/64331] " senthil_kumar.selvaraj at atmel dot com
2014-12-16 14:31 ` [Bug target/64331] " rguenth at gcc dot gnu.org
2014-12-16 16:24 ` ebotcazou at gcc dot gnu.org
2014-12-17  2:34 ` senthil_kumar.selvaraj at atmel dot com
2014-12-17 15:12 ` ebotcazou at gcc dot gnu.org [this message]
2015-02-20 17:11 ` gjl at gcc dot gnu.org
2015-03-03 11:10 ` gjl at gcc dot gnu.org
2015-03-03 11:25 ` gjl at gcc dot gnu.org
2015-03-03 11:36 ` gjl at gcc dot gnu.org
2015-04-22 12:01 ` jakub at gcc dot gnu.org
2015-07-16  9:18 ` rguenth at gcc dot gnu.org
2015-09-28 16:27 ` olegendo at gcc dot gnu.org
2022-01-09  0:43 ` pinskia at gcc dot gnu.org
2023-05-28 17:02 ` gjl at gcc dot gnu.org
2023-05-28 17:02 ` gjl 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-64331-4-3WS7pFTkbV@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: link
Be 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).