From: Kaz Kojima <kkojima@rr.iij4u.or.jp>
To: stevenb.gcc@gmail.com
Cc: gcc@gcc.gnu.org, zadeck@naturalbridge.com
Subject: Re: A question about df_get_live_in
Date: Mon, 13 Jul 2009 23:17:00 -0000 [thread overview]
Message-ID: <20090714.081700.128123313.kkojima@rr.iij4u.or.jp> (raw)
In-Reply-To: <571f6b510907131507y6824fe4n6932b3ea26e85527@mail.gmail.com>
[I'd like to add kenny to the CC list.]
Steven Bosscher <stevenb.gcc@gmail.com> wrote:
> So when the CFG is still valid, r15 is live-out in basic block 2 and
> live-in in basic block 3 (which contains insns 32, whatever that means
> for an invalid CFG). For which bb does mark_target_live_regs call
> df_get_live_in?
gdb says
920 b = find_basic_block (target, MAX_DELAY_SLOT_LIVE_SEARCH);
returns 2.
Regards,
kaz
next prev parent reply other threads:[~2009-07-13 23:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-13 21:46 Kaz Kojima
2009-07-13 22:08 ` Steven Bosscher
2009-07-13 23:17 ` Kaz Kojima [this message]
2009-07-13 23:37 ` Steven Bosscher
2009-07-13 23:52 ` Eric Botcazou
2009-07-14 0:13 ` Kaz Kojima
2009-07-14 12:20 ` Eric Botcazou
2009-07-14 12:50 ` Kaz Kojima
2009-07-14 5:20 ` Jeff Law
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=20090714.081700.128123313.kkojima@rr.iij4u.or.jp \
--to=kkojima@rr.iij4u.or.jp \
--cc=gcc@gcc.gnu.org \
--cc=stevenb.gcc@gmail.com \
--cc=zadeck@naturalbridge.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).