From: Kenneth Zadeck <zadeck@naturalbridge.com>
To: Steven Bosscher <stevenb.gcc@gmail.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch] Make df_ref point to a df_insn_info instead of an insn rtx
Date: Wed, 18 Jun 2008 05:34:00 -0000 [thread overview]
Message-ID: <48588C3A.5020703@naturalbridge.com> (raw)
In-Reply-To: <571f6b510806171620i519d4501r67aa365de6c0ceec@mail.gmail.com>
Steven Bosscher wrote:
> Hi,
>
> This is the patch to change how df_refs point to their insns. Without
> this patch, a df_ref points directly to the insn's rtx. And from the
> insn, we get the df_insn_info via DF_INSN_GET, which points to the
> insn def and use refs.
>
> But if we are going to have fake insns that have defs and uses, but no
> real insns (e.g. PHI nodes), we need a different way to find the
> sibling defs/uses for a given reference. The easiest way is to just
> point directly at the df_insn_info for the insn that contains the
> reference. This way, we can then still point at a df_insn_info for
> fake insns.
>
> Attached patch was bootstrapped&tested on ia64-unknown-linux-gnu (and
> an earlier equivalent version on powerpc). Kenny, what do you think
> about this? OK for trunk?
>
> Gr.
> Steven
>
one comment:
ChangeLog: s/df_code.c/df_core.c/
fine for commit to trunk.
i bootstrapped this on ia-64 just to make sure that the ia-64 only
passes were properly changed.
kenny
prev parent reply other threads:[~2008-06-18 4:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-17 23:37 Steven Bosscher
2008-06-18 5:34 ` Kenneth Zadeck [this message]
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=48588C3A.5020703@naturalbridge.com \
--to=zadeck@naturalbridge.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=stevenb.gcc@gmail.com \
/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).