-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/21/11 21:28, Hans-Peter Nilsson wrote:
> 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
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
On Wed, Jun 15, 2011 at 9:26 PM, Jeff Law wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
>
>
> 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 thre
On Thu, Jun 16, 2011 at 6:26 AM, Jeff Law wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
>
>
> 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 thre
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
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 b
On Thu, May 5, 2011 at 6:11 PM, Jeff Law wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> I should have included these in the last patch of infrastructure changes.
>
> The main change is create_block_for_threading no longer calls
> remove_ctrl_stmt_and_useless_edges and instead its c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I should have included these in the last patch of infrastructure changes.
The main change is create_block_for_threading no longer calls
remove_ctrl_stmt_and_useless_edges and instead its callers are expected
to handle that, when needed. This will al
