llvm dev - Apr 2010 - [LLVMdev] Status of Strong PHI Elimination?

Hello,

I am implementing a code transformation that would heavily benefit from the
CodeGen/StrongPHIElimination pass, but on the two bytecode files I've tested
it on so far llc segfaults on both.  I see there have been no substantive
changes to this code since the middle of last year.  Could someone please
tell me what the status of this pass is?  Thank you.

Marc
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20100427/a14a0627/attachment.html>

On Apr 27, 2010, at 2:17 PM, Marc de Kruijf wrote:
> Hello,
> 
> I am implementing a code transformation that would heavily benefit from the
CodeGen/StrongPHIElimination pass, but on the two bytecode files I've tested
it on so far llc segfaults on both.  I see there have been no substantive
changes to this code since the middle of last year.  Could someone please tell
me what the status of this pass is?  Thank you.
It's not production quality so I wouldn't recommend using it.

Evan
> 
> Marc
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev

Hi Marc,
> I am implementing a code transformation that would heavily benefit from
> the CodeGen/StrongPHIElimination pass, but on the two bytecode files
> I've tested it on so far llc segfaults on both.  I see there have been
> no substantive changes to this code since the middle of last year.
> Could someone please tell me what the status of this pass is?  Thank you.
I don't know what the status is, but filing bug reports with the problematic
testcases will hopefully get things moving.

Ciao,

Duncan.

On Apr 27, 2010, at 2:17 PM, Marc de Kruijf wrote:
> Hello,
> 
> I am implementing a code transformation that would heavily benefit from the
CodeGen/StrongPHIElimination pass, but on the two bytecode files I've tested
it on so far llc segfaults on both.  I see there have been no substantive
changes to this code since the middle of last year.  Could someone please tell
me what the status of this pass is?  Thank you.
As you discovered, it's buggy, incomplete and, to my knowledge, not being
worked on.

--Owen