From: Eric Botcazou <ebotcazou@adacore.com>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: fwprop: fix REG_DEAD notes rendered incorrect
Date: Thu, 27 Oct 2011 14:58:00 -0000 [thread overview]
Message-ID: <201110271532.17592.ebotcazou@adacore.com> (raw)
In-Reply-To: <orr51y3744.fsf@livre.localdomain>
> fwprop may propagate a SET_SRC that contains the last use of a REG to a
> later point, but it will leave the REG_DEAD note in place, even though
> it is no longer correct. I noticed this while investigating PR50826:
> the initialization of the internal_arg_pointer has a REG_DEAD note for
> %r29, but even after it is fwpropped, the note remains there. This
> patch fixes this bug.
This isn't necessarily a bug, i.e. passes aren't required to maintain REG_DEAD
and REG_UNUSED notes up-to-date (another example is PR rtl-opt/48773). Instead
passes consuming these notes have to invoke df_note_add_problem on entry.
--
Eric Botcazou
next prev parent reply other threads:[~2011-10-27 13:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-27 13:32 Alexandre Oliva
2011-10-27 14:58 ` Eric Botcazou [this message]
2011-10-27 16:46 ` Alexandre Oliva
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=201110271532.17592.ebotcazou@adacore.com \
--to=ebotcazou@adacore.com \
--cc=aoliva@redhat.com \
--cc=gcc-patches@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).