search for: createphi

Hi, all I'd like to write a code that can build different codes based on LLVM version. Like code snippets in the below. #ifdef __LLVM_29__ PHINode *PN = Builder.CreatePHI (Type::getDoubleTy(getGlobalContext()), 2, "iftmp"); #elif __LLVM_28__ PHINode *PN = Builder.CreatePHI (Type::getDoubleTy(getGlobalContext()), "iftmp"); #else assert ("wrong version"); #endif I've been trying to find something like these (__LLVM_29__, __LLVM...

...m::DITemplateParameter>, llvm::DISubprogram*)", referenced from: (anonymous namespace)::FunctionAST::codegen() in toy-1f302b.o "vtable for llvm::PHINode", referenced from: llvm::IRBuilder<true, llvm::ConstantFolder, llvm::IRBuilderDefaultInserter<true> >::CreatePHI(llvm::Type*, unsigned int, llvm::Twine const&) in toy-1f302b.o NOTE: a missing vtable usually means the first non-inline virtual member function has no definition. ld: symbol(s) not found for architecture x86_64 clang-3.8: error: linker command failed with exit code 1 (use -v to see invocatio...

Kangkook Jee <aixer77 at gmail.com> writes: > Hi, all > > I'd like to write a code that can build different codes based on LLVM version. > Like code snippets in the below. > > #ifdef __LLVM_29__ > PHINode *PN = Builder.CreatePHI (Type::getDoubleTy(getGlobalContext()), 2, "iftmp"); > #elif __LLVM_28__ > PHINode *PN = Builder.CreatePHI (Type::getDoubleTy(getGlobalContext()), "iftmp"); > #else > assert ("wrong version"); > #endif > > I've been trying to find somethi...

...y invalid) programs. > Any attempt > by the frontend to emit variables in true SSA form is just > duplicating this > optimization — in the case of dragonegg, because the SSA conversion is > implicit in how gcc creates the IR it lowers from. Makes sense. However, grep'ing on CreatePHI in clang's CodeGen module I see several places where clang's 'front-end' is doing this. What is the rational for that? - Fariborz > > > John. > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu ht...

On Sep 13, 2010, at 1:15 AM, Duncan Sands wrote: >> I compiled with "llvm-gcc -emit-llvm test.c -S -o test.ll". Attached to this >> message are the source and the resulting ll output. > > compile with optimization. The llvm-gcc front-end "cheats" and stores/loads all > values to/from memory, avoiding the need to construct phi nodes; instead it lets >

...d) programs. Any attempt >> by the frontend to emit variables in true SSA form is just duplicating this >> optimization — in the case of dragonegg, because the SSA conversion is >> implicit in how gcc creates the IR it lowers from. > > Makes sense. However, grep'ing on CreatePHI in clang's CodeGen module I see several > places where clang's 'front-end' is doing this. What is the rational for that? We do emit phis when the semantics aren't defined in terms of memory, e.g. with expressions that have multiple paths of control flow (like the conditiona...