similar to: [LLVMdev] Build fails on windows using VS2008

On Mon, 12 Feb 2007, Carsten Reuter wrote: > I am trying to build and install LLVM onto a current Debian Linux system > using gcc4 frontend binaries for Red Hat Enterprise Linux4/x86 . > Using the commands below the Build finishes, ignoring an error that > comes up again when I try to make install. > See the messages below. I have no good feeling about the "-i -k" options.

Hi, I am trying to build and install LLVM onto a current Debian Linux system using gcc4 frontend binaries for Red Hat Enterprise Linux4/x86 . Using the commands below the Build finishes, ignoring an error that comes up again when I try to make install. See the messages below. I have no good feeling about the "-i -k" options. Is it OK? Thank you in advance for any advice and best

Attempting to build the latest llvm I get: llvm[2]: Linking Debug+Asserts executable opt C:/Utilities/MSYS/build/llvm/Debug+Asserts/lib/libLLVMScalarOpts.a(SimplifyLibCalls.o):C:/Programming/VersionControl/llvm/include/llvm/Instructions.h:388: undefined reference to `llvm::GetElementPtrInst::GetElementPtrInst(llvm::Value*, llvm::Value*, llvm::Twine const&, llvm::Instruction*)'

Hi all. I'm working on a LLVM based compiler for the D programming language by Walter Bright. D allows static arrays up to 16MB in size. I'm initializing global static arrays with a constant initializer. But D requires that (per default) static arrays are initialized with the default initializer for the element type. For float this happens to be NaN, so I cannot use a

David Greene wrote: > We've upgraded to llvm 2.4 and we're hitting an assert in SCEV: > > llvm/include/llvm/Analysis/ScalarEvolutionExpressions.h:669: RetVal > llvm::SCEVVisitor<SC, > RetVal>::visitCouldNotCompute(llvm::SCEVCouldNotCompute*) [with SC = > llvm::SCEVExpander, RetVal = llvm::Value*]: Assertion `0 && "Invalid use of >

We've upgraded to llvm 2.4 and we're hitting an assert in SCEV: llvm/include/llvm/Analysis/ScalarEvolutionExpressions.h:669: RetVal llvm::SCEVVisitor<SC, RetVal>::visitCouldNotCompute(llvm::SCEVCouldNotCompute*) [with SC = llvm::SCEVExpander, RetVal = llvm::Value*]: Assertion `0 && "Invalid use of SCEVCouldNotCompute!"' failed. This happens in

On Friday 27 February 2009 00:50, Nick Lewycky wrote: > David Greene wrote: > > We've upgraded to llvm 2.4 and we're hitting an assert in SCEV: > > > > llvm/include/llvm/Analysis/ScalarEvolutionExpressions.h:669: RetVal > > llvm::SCEVVisitor<SC, > > RetVal>::visitCouldNotCompute(llvm::SCEVCouldNotCompute*) [with SC = > > llvm::SCEVExpander,

2 new warnings in llvm: /Volumes/mrs5/net/llvm/llvm/lib/AsmParser/LLParser.cpp: In member function 'bool llvm::LLParser::ParseGlobal(const std::string&, const char*, unsigned int, bool, unsigned int)': /Volumes/mrs5/net/llvm/llvm/lib/AsmParser/LLParser.cpp:446: warning: 'IsConstant' may be used uninitialized in this function

Hello all, I am a LLVM newer who want to add a new backend(EBC) into LLVM. After coping the related files from another target and modifying it, I meet a problem when I build the project. The error message is as follows: ================================================================ [ 94%] Built target llvm-dis Linking CXX executable ../../bin/llvm-mc Undefined symbols:

Hello, Ferad. > `.gnu.linkonce.t._ZN4llvm12SCEVExpander6expandEPNS_4SCEVE' referenced > in section `.rodata' of > /home/ferad/llvm/llvm-obj/Release/lib/libLLVMAnalysis.a(ScalarEvolutionExpander.o): > defined in discarded section > `.gnu.linkonce.t._ZN4llvm12SCEVExpander6expandEPNS_4SCEVE' of >

Does not seem to be a straight error with LLVM itself, but rather the tools, linking issues, here are the errors: Opt: 30> Creating library R:\SDKs\llvm\trunk_VC8_building\lib\Debug\opt.lib and object R:\SDKs\llvm\trunk_VC8_building\lib\Debug\opt.exp 30>LLVMScalarOpts.lib(IndVarSimplify.obj) : error LNK2019: unresolved external symbol "public: bool __thiscall

Guys, What I want to do is to hack global opt pass, which needs ScalarEvolution analysis. However opt crashed saying "opt: /home/xchen/llvm/include/llvm/PassAnalysisSupport.h:242: AnalysisType& llvm::Pass::getAnalysisID(const void*, llvm::Function&) [with AnalysisType = llvm::ScalarEvolution]: Assertion `ResultPass && "Unable to find requested analysis info"'

Hi, I got upset.. What does “Broken module found, compilation aborted!” mean really?? what‘s “broken module“?? -- 祝好！ 甄凯 ------------------------------------------------------------------------------------------------------ 2012-04-09 ------------------------------------------------------------------------------------------------------ Name: 甄凯(ZhenKai)

First, thanks for testing this! > Here's the results for GNU/Linux, 2.6.18-1.2200.fc5smp (Fedora Core 5) > > HIGH LEVEL COMMENTS > * The llvm-1.9.tar.gz file unpacks to a dir named "llvm". Shouldn't > that be llvm-1.9? We have always labeled the dir just llvm which is fine. If you build llvm it will know its version 1.9. > * LLVM was built in Release mode

Hi all， Im trying to instrument this hello function right before the instruction that call the "puts" function(the source code is as follow). Now I can compile the pass without errors, but when run the pass with opt tool, it broke down. The diagnose is something like Referencing function in another module! %CallCheck = call i32 @fib() Broken module found, compilation aborted! Does

Thank you very much! To make it simpler, I may as well just implement the self-written "check function" in C language instead of wrapping it in LLVM module. According to the hint you give me, all I need to do is as follow(?) 1. Implement the "Check function" in the check.c file; 2. Add the check function into the module(the Hello1.bc file which I will run the functionPass on)

Tanya, Here's the results for GNU/Linux, 2.6.18-1.2200.fc5smp (Fedora Core 5) HIGH LEVEL COMMENTS * The llvm-1.9.tar.gz file unpacks to a dir named "llvm". Shouldn't that be llvm-1.9? * LLVM was built in Release mode in all cases * I don't think this is ready for release. In particular the llvm-gcc4 binary seg faults on FC 5 for most of llvm-test programs. *

That sounds like a good general plan, yes! Joey 2012/4/9 15102925731 <zhenkaixd at 126.com> > Thank you very much! > > To make it simpler, I may as well just implement the self-written "check > function" in C language instead of wrapping it in LLVM module. *According > to the hint you give me, all I need to do is as follow(?)* > > 1. Implement the

Hi, I don't think the code you pasted can be the correct code, where does FibF come from? Anyway, the problem is that you're calling the FibF from Module A, however you defined it for Module B. You need to insert the FibF function into the Module that you're running. To do this override "virtual bool doInitialization(Module &M);" and insert FibF into M. Joey 2012/4/9

Hello, everyone! Recently, I build llvm project for Visual Studio 2008 using cmake successfulley. I modify the project LLVMHello of the entire solution to generate LLVMHello.dll instead of LLVMHello.lib without other changes. Then, the flowing commands is executed: opt -load LLVMHello.dll --help But, I can't find the information string for hello pass. opt -load LLVMHello.dll