search for: memdepprint

Hi All, Looking at the code of MemDepPrinter.cpp, I saw the char MemDepPrinter::ID = 0; > INITIALIZE_PASS_BEGIN(MemDepPrinter, "print-memdeps", > "Print MemDeps of function", false, true) > INITIALIZE_PASS_DEPENDENCY(MemoryDependenceAnalysis) > INITIALIZE_PASS_END(MemDepPrinter, "print-memdeps", &g...

...ended up trying to run opt over part of the code of bzip2 from SPEC 2006, but unfortunately an assertion fail prevents it from finishing the analysis: Assertion failed: (dep.isUnknown() && "unexpected dependence type"), function getInstTypePair, file /Developer/llvm/lib/Analysis/MemDepPrinter.cpp, line 70. Stack dump: 0. Program arguments: /Developer/llvm/build/bin/opt -aa -aa-eval -basicaa -cfl-aa -external-aa -globals-aa -objc-arc-aa -print-alias-sets -scev-aa -scoped-noalias -tbaa -da -memdep -print-memdeps build_base_yosemite.0000/blocksort.bc -debug-pass=Structure -disable-output...

I used LLVM already existent passes with no problems till I tried to use MemDepPrinter.cpp : http://llvm.org/doxygen/MemDepPrinter_8cpp_source.html. I got the following segfault: llvm[0]: Compiling MyMemDepPrinter.cpp for Release+Asserts build (PIC) llvm[0]: Linking Release+Asserts Loadable Module MyMemDepPrinter.so WARNING: You're attempting to print out a bitcode...

Philip Reames wrote: > T.M.K., there's no direct way to test it. There is. See the 'unittests/' directory which contains the C++ unit tests. See unittests/IR/UserTest.cpp for an example that builds up IR from a .ll-in-a-C-string then queries C++ API operations on it. Nick You have to construct a > transformation which happens with the information you added and not >

...rkill. > Fifth, some pointers on debugging this yourself. GVN (which is the one > which does complicated *-load forwarding) calls MDA > (MemoryDepedenceAnalysis). Using the appropriate -debug-only options will > likely get you to the right area. You can also consider using the > MemDepPrinter pass to bypass GVN. I don't know of a way to issue raw AA > queries for testing. That would be useful, but I don't know that we have > it. > > Hope that helps. > > Yes, thanks. I'll probably come back with more question once I've played with these options a bit...

I'm trying to fix that bug: https://llvm.org/bugs/show_bug.cgi?id=20049 It turns out this is the kind of optimization that I really need, as when it isn't done, all kind of other optimizations opportunities down the road are not realized as they are not exposed. I have no idea where to start digging for this. I assume there is some kind of interaction between memory dependency and alias

...ers on debugging this yourself. GVN (which is > the one which does complicated *-load forwarding) calls MDA > (MemoryDepedenceAnalysis). Using the appropriate -debug-only > options will likely get you to the right area. You can also > consider using the MemDepPrinter pass to bypass GVN. I don't > know of a way to issue raw AA queries for testing. That would > be useful, but I don't know that we have it. > > Hope that helps. > > > Yes, thanks. I'll probably come back with more question once I'v...

...pp for Release+Asserts build llvm[3]: Compiling ScheduleDAGSDNodes.cpp for Release+Asserts build llvm[3]: Compiling SimplifyCFG.cpp for Release+Asserts build llvm[2]: Compiling LoopPass.cpp for Release+Asserts build llvm[3]: Compiling ScheduleDAGVLIW.cpp for Release+Asserts build llvm[2]: Compiling MemDepPrinter.cpp for Release+Asserts build llvm[3]: Compiling X86AsmPrinter.cpp for Release+Asserts build llvm[3]: Compiling SelectionDAG.cpp for Release+Asserts build llvm[2]: Compiling MemDerefPrinter.cpp for Release+Asserts build llvm[2]: Compiling MemoryBuiltins.cpp for Release+Asserts build llvm[3]: Comp...