From: Hans-Peter Nilsson <hp@bitrange.com>
To: Eric Botcazou <ebotcazou@adacore.com>
Cc: gcc-patches@gcc.gnu.org, rdsandiford@googlemail.com
Subject: Re: dbr_schedule vs uninitialized registers (2)
Date: Tue, 28 Apr 2009 07:28:00 -0000 [thread overview]
Message-ID: <20090428021136.X48564@dair.pair.com> (raw)
In-Reply-To: <200904271247.00652.ebotcazou@adacore.com>
On Mon, 27 Apr 2009, Eric Botcazou wrote:
> 2009-04-27 Richard Sandiford <rdsandiford@googlemail.com>
> Eric Botcazou <ebotcazou@adacore.com>
>
> * resource.c (find_basic_block): Use BLOCK_FOR_INSN to look up
> a label's basic block.
> (mark_target_live_regs): Tidy and rework obsolete comments.
> Change back DF problem to LIVE. If a label starts a basic block,
> assume that all registers that used to be live then still are.
> (init_resource_info): If a label starts a basic block, set its
> BLOCK_FOR_INSN accordingly.
> (free_resource_info): Undo the setting of BLOCK_FOR_INSN.
This caused PR39938.
brgds, H-P
prev parent reply other threads:[~2009-04-28 6:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 10:46 Eric Botcazou
2009-04-28 7:28 ` Hans-Peter Nilsson [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=20090428021136.X48564@dair.pair.com \
--to=hp@bitrange.com \
--cc=ebotcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rdsandiford@googlemail.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).