Curtis Rawls wrote:
This patch adds a bb_remove_edge() function, and decouples unreachable blocks
from the CFG by removing their successor edges.
Thanks, applied - r8913
leo
Patch attached.
On 8/10/05, Curtis Rawls <[EMAIL PROTECTED]> wrote:
> I have attached a patch that fixes this problem.
>
> Description:
> -
> This patch adds a bb_remove_edge() function, and decouples unreachable blocks
> from the CFG by removing their successor edges.
> -
>
> I think th
I have attached a patch that fixes this problem.
Description:
-
This patch adds a bb_remove_edge() function, and decouples unreachable blocks
from the CFG by removing their successor edges.
-
I think this is the best way to handle unreachable blocks in the CFG,
other than removing them, w
Patrick R. Michaud wrote:
... I'm able to reproduce this
with the code below
Good catch.
I'll be very happy to add the above PIR segment to the imcc test
suite if someone can tell me which imcc/t/*/*.t file it should go in.
Probably time to start a new subdir:
imcc/t/cfg/df.t
or some
On Thu, Jul 28, 2005 at 03:39:33PM -0400, Andy Dougherty wrote:
> On Thu, 28 Jul 2005, Will Coleda wrote:
>
> > Applying your patch to a pristine build yields only the backtrack.t failure:
> > #2 eats 100% of the CPU until I kill it: it doesn't behave that way in
> > svn-head.
>
> I can confirm t
Thanks for pointing this out. I tracked the bug down, and it looks
like the dominator algorithm does not handle unreachable blocks
correctly, and the dominance frontier algorithm suffers for it. Why
the unreachable blocks are generated in the first place might be an
interesting question for someo
On Thu, 28 Jul 2005, Will Coleda wrote:
> Applying your patch to a pristine build yields only the backtrack.t failure:
> #2 eats 100% of the CPU until I kill it: it doesn't behave that way in
> svn-head.
I can confirm the backtrack #2 failure under SPARC/Solaris. I can't say
what other tests ma
The eval tests are failing with a pristine checkout so we can ignore
those. Applying your patch to a pristine build yields only the
backtrack.t failure: #2 eats 100% of the CPU until I kill it: it
doesn't behave that way in svn-head.
Looks like PerlString and String were red herrings. Shoul
FYI, on OS X 10.4.2, I get:
Failed Test Stat Wstat Total Fail Failed List of Failed
---
t/p6rules/backtrack.t1 256151 6.67% 2
t/pmc/eval.t 3 768143 21.43% 12-14
t/pm
Can someone apply this? I have another patch ready that depends on this one.
Thanks!
-Curtis
On 7/19/05, via RT Curtis Rawls <[EMAIL PROTECTED]> wrote:
> # New Ticket Created by Curtis Rawls
> # Please include the string: [perl #36597]
> # in the subject line of all future correspondence about
10 matches
Mail list logo
