From: Steven Bosscher <stevenb.gcc@gmail.com>
To: Richard Henderson <rth@redhat.com>
Cc: GCC Mailing List <gcc@gcc.gnu.org>
Subject: Re: Question about dead_or_predicable
Date: Thu, 25 Jun 2009 13:09:00 -0000 [thread overview]
Message-ID: <571f6b510906250032k9c638e9w45204b1be3b8b677@mail.gmail.com> (raw)
In-Reply-To: <4A4247BF.5090400@redhat.com>
On Wed, Jun 24, 2009 at 5:35 PM, Richard Henderson<rth@redhat.com> wrote:
> Have a quick look at the implementation of invert_jump, and both
> questions are quickly answered.
Heh, well, all those functions in jump.c also really confuse me --
probably because I've never really understood how all the functions to
change RTL work. But OK, I understand what is going on now, thanks.
> All that said, I think your plan to rearrange things to allow both
> CE and NCE paths to be followed is fine. You'll just need to dup
> that jump change into both paths so that the CE path change group
> gets its own shot at rejecting the jump change.
Right. I think I'll do it with a verify_changes() check at the end of
the CE path, that should result in a smaller patch.
Thanks for your help,
Ciao!
Steven
prev parent reply other threads:[~2009-06-25 7:32 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
2009-06-24 7:06 ` Steven Bosscher
2009-06-24 16:22 ` Richard Henderson
2009-06-25 13:09 ` Steven Bosscher [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=571f6b510906250032k9c638e9w45204b1be3b8b677@mail.gmail.com \
--to=stevenb.gcc@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=rth@redhat.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).