On 11/22/13 13:05, Steven Bosscher wrote:
On Fri, Nov 22, 2013 at 11:09 AM, Jeff Law wrote:
So we've long had an arbitrary restriction in the jump thread identification
code which made it very conservative when searching for threading
opportunities once it encountered a back edge.
You're addi
On Fri, Nov 22, 2013 at 11:09 AM, Jeff Law wrote:
>
> So we've long had an arbitrary restriction in the jump thread identification
> code which made it very conservative when searching for threading
> opportunities once it encountered a back edge.
You're adding a pretty complex piece of code, for
There was a typo/thinko in the version I posted last night (reversed
arguments to a bitmap_copy call) that I spotted this morning. Those
were some of the newer bits to get the maps reset after handling each
successor of a joiner block.
So re-bootstrapped and re-regression tested on x86_64-u
It's amazing what 10 years away from a hunk of code will do...
So we've long had an arbitrary restriction in the jump thread
identification code which made it very conservative when searching for
threading opportunities once it encountered a back edge.
I've always known the problem was poll
