From: Dave Korn <dave.korn.cygwin@googlemail.com>
To: Steven Bosscher <stevenb.gcc@gmail.com>
Cc: Richard Henderson <rth@redhat.com>, GCC Mailing List <gcc@gcc.gnu.org>
Subject: Re: Question about dead_or_predicable
Date: Wed, 24 Jun 2009 02:45:00 -0000 [thread overview]
Message-ID: <4A416A23.9000506@gmail.com> (raw)
In-Reply-To: <571f6b510906231527h453fe581i5cf85b785b587b86@mail.gmail.com>
Steven Bosscher wrote:
> The comment doesn't explain *why* we don't want delete_insn to be
> called, or why we want to do our own change group management.
dead_or_predicable is called from find_if_case_[12] which is called from
find_if_header which is called from if_convert within a FOR_EACH_BB loop; is
this perhaps another example of "don't mess with something while you're
iterating over it or your iterator might break"?
cheers,
DaveK
next prev parent reply other threads:[~2009-06-23 23:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-23 22:50 Steven Bosscher
2009-06-24 2:45 ` Dave Korn [this message]
2009-06-24 7:06 ` Steven Bosscher
2009-06-24 16:22 ` Richard Henderson
2009-06-25 13:09 ` Steven Bosscher
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=4A416A23.9000506@gmail.com \
--to=dave.korn.cygwin@googlemail.com \
--cc=gcc@gcc.gnu.org \
--cc=rth@redhat.com \
--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).