search for: structurizecfg

Hi, I'm trying to solve a problem from StructurizeCFG not actually handling regions with multiple exits. Sample IR attached. StructurizeCFG doesn't touch this function, exiting early on the isTopLevelRegion check. SIAnnotateControlFlow then gets confused and ends up inserting an if into one of the blocks, and the matching end.cf into one of t...

Hi, I've been investigating the StructurizeCFG pass, and it looks like it has trouble handling CFG edges that break out of a loop and go directly to the function exit. Am I running up against a bug in the structurizer, or a general limitation of the algorithm used? As an aside, is there any documentation for the algorithm used? Is it based o...

On Sat, Oct 14, 2017 at 11:05 AM, John Regehr via llvm-dev <llvm-dev at lists.llvm.org> wrote: > These are definitely LLVM bugs. It would be best to report reduced test > cases against top of tree. > > We should have some automated infrastructure for finding these too... > > John > Zhendong & friends generally do that (and reported many bugs :) I tried that myself,

...easier to setup some build bots. Thank you, Filipe On Fri, Apr 22, 2016 at 8:40 PM, Geoff Berry via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Bugs filed: > 27488 <https://llvm.org/bugs/show_bug.cgi?id=27488> librarie Scalar O > unassignedbugs at nondot.org NEW --- [StructurizeCFG] lit test hits assert > in verifyDomTree when compiled w/ XDEBUG > <https://llvm.org/bugs/show_bug.cgi?id=27488> 14:34:06 > 27487 <https://llvm.org/bugs/show_bug.cgi?id=27487> librarie Scalar O > unassignedbugs at nondot.org NEW --- [LoopVersioning] lit test hits invalid &gt...

...m loop exit    if (B[j] > 50) { // uniform branch      C[j][thread_id] = 42;    }    if (D[j] < V) break; // divergent loop exit  }  x = j; // divergent (temporal; due to divergent loop) } -- Motivation -- The LoopVectorizer and VPlan currently use SCEV to detect uniform values. The StructurizeCFG pass and the AMDGPU backends rely on LLVM’s existing DivergenceAnalysis pass for SPMD kernels. Both approaches have shortcomings that are resolved by the new analysis. - Why the current DivergenceAnalysis is broken - LLVM already includes a DivergenceAnalysis for GPU kernels. It is used in th...

Yeah, they are just triggered by lit check tests. I’ll file some bugs today, though it looks like Quentin may have already filed bugs for some of these. -- Geoff Berry Employee of Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project From: Daniel Berlin [mailto:dberlin at dberlin.org] Sent: Friday,

Hi Tobias, Thanks a lot for the detailed reply. I am working on several new optimizations for OpenCL kernels for a DSP architecture. The project itself has an NDA associated with it, so I cannot go into more details, but the source will be open to public after completion. One of the first steps is to serialize the work-items in a work-group (e.g., insert nested loops around REGIONs in

...n California next week, let's chat! > > We could make use of the autotuner I'm currently building: > > https://github.com/kavon/autotune > > It tries to find an optimal sequence of IR passes, and I've run into a bunch of different bugs with it so far (e.g., it seems structurizecfg interacts poorly with 'invoke'). I'll start submitting bug reports for them soon. As part of the stress-suite of the LLVM obfuscator we're going to present next Thursday, we ran into similar problems. Well, when you s/optimization/obfuscation/ many things go wrong anyway. I'm...

...ionInfo class. If it's not much trouble, could you send the >> draft to my forum email? Also, are you aware of any plan on having the >> interval/structural analysis supported in LLVM. Thanks again. >> > > Maybe this is interesting to you: > > lib/Transforms/Scalar/StructurizeCFG.cpp > > > P.S. One thing I need to find out from reading the implementation is why a >> sequence of basic blocks do not get to form a region as a whole. >> > > A sequence of basic blocks can form a region. The reason the RegionInfo > does not form such reason is that...

...Asserts build llvm[3]: Compiling StraightLineStrengthReduce.cpp for Release+Asserts build llvm[3]: Compiling BarrierNoopPass.cpp for Release+Asserts build llvm[2]: Compiling DFAPacketizer.cpp for Release+Asserts build llvm[3]: Compiling ConstantMerge.cpp for Release+Asserts build llvm[3]: Compiling StructurizeCFG.cpp for Release+Asserts build llvm[3]: Compiling DeadArgumentElimination.cpp for Release+Asserts build llvm[2]: Compiling DeadMachineInstructionElim.cpp for Release+Asserts build llvm[2]: Compiling DwarfEHPrepare.cpp for Release+Asserts build llvm[3]: Compiling RuntimeDyldMachO.cpp for Release+Asse...