From: Hans-Peter Nilsson <hp@bitrange.com>
To: Jeff Law <law@redhat.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: Improve jump threading #5 of N
Date: Wed, 22 Jun 2011 04:19:00 -0000 [thread overview]
Message-ID: <alpine.BSF.2.00.1106212325410.48489@dair.pair.com> (raw)
In-Reply-To: <4DF985ED.30406@redhat.com>
On Wed, 15 Jun 2011, Jeff Law wrote:
> So as I've mentioned previously, I've been working on a relatively small
> change to the jump threading code which would allow it to duplicate a
> join block when doing so allows us to thread through a successor of the
> join block. This is expected to be the last extension to the existing
> jump threading code.
> Bootstrapped and regression tested on x86_64-unknown-linux-gnu.
It seems this caused a warning regression, PR49498, for some
but not all targets, see the PR.
brgds, H-P
next prev parent reply other threads:[~2011-06-22 3:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-16 5:49 Jeff Law
2011-06-16 7:57 ` Richard Guenther
2011-06-19 7:30 ` H.J. Lu
2011-06-22 4:19 ` Hans-Peter Nilsson [this message]
2011-06-22 14:13 ` 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=alpine.BSF.2.00.1106212325410.48489@dair.pair.com \
--to=hp@bitrange.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@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).