search for: seversplitphinod

> From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] > On Behalf Of Wei Dang > Subject: [LLVMdev] Question about method CodeExtractor::severSplitPHINodes > In the implementation of serverSplitPHINodes(), why it only checks the > first PHI node for possible multiple inputs from outside the region to > extract. There could be more than one PHI nodes in the header block, > and the code only checks the first one. I don't quite get i...

> From: Wei Dang [mailto:jacdang at gmail.com] > Subject: Re: [LLVMdev] Question about method CodeExtractor::severSplitPHINodes > Please excuse me if I'm not supposed to reply to all. You should do reply-all, to make sure the list sees all of the thread. > Are you saying all PHI nodes are required to include all its predecessor blocks > no matter they have input or not? That's the way SSA works - eac...

Hi, I found a problem in CodeExtractor::severSplitPHINodes() <CodeExtractor.cpp>. The algorithm first separates the header block into two, one containing only PHI nodes and the other containing the remaining non-PHI nodes. The variable NewBB holds the pointer to the latter half block. Later, it tries to update DT information. if (DT) DT->s...

...s a lot. On Sat, Mar 2, 2013 at 6:39 PM, Caldarale, Charles R < Chuck.Caldarale at unisys.com> wrote: > > From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] > > On Behalf Of Wei Dang > > Subject: [LLVMdev] Question about method > CodeExtractor::severSplitPHINodes > > > In the implementation of serverSplitPHINodes(), why it only checks the > > first PHI node for possible multiple inputs from outside the region to > > extract. There could be more than one PHI nodes in the header block, > > and the code only checks the first one. I...

On Nov 19, 2008, at 7:41 AM, Jack Tzu-Han Hung wrote: > Hi, > > I found a problem in CodeExtractor::severSplitPHINodes() > <CodeExtractor.cpp>. > > The algorithm first separates the header block into two, one > containing only PHI nodes and the other containing the remaining non- > PHI nodes. The variable NewBB holds the pointer to the latter half > block. Later, it tries to update...

...contains exit(1). ExtractLoop() has problem with this this example. Thanks a lot. Jack On Wed, Nov 19, 2008 at 7:41 PM, Devang Patel <dpatel at apple.com> wrote: > > On Nov 19, 2008, at 7:41 AM, Jack Tzu-Han Hung wrote: > > Hi, > > I found a problem in CodeExtractor::severSplitPHINodes() > <CodeExtractor.cpp>. > > The algorithm first separates the header block into two, one containing > only PHI nodes and the other containing the remaining non-PHI nodes. The > variable NewBB holds the pointer to the latter half block. Later, it tries > to update DT infor...

...s from inside. Then what's the point of adding it as an incoming value to the new PHI when it doesn't even have anything from outside. This looks redundant to me. I could only guess it has something to do with the way PHI nodes get inserted in LLVM. Any help is much appreciated!!! /// severSplitPHINodes - If a PHI node has multiple inputs from outside of the00185 /// region, we need to split the entry block of the region so that the PHI node00186 /// is easier to deal with.00187 void CodeExtractor::severSplitPHINodes(BasicBlock <http://llvm.org/docs/doxygen/html/classllvm_1_1BasicBlock.html&g...