search for: msilwrit

...ter::executeGEPOperation(llvm::Value*, llvm::gep_type_iterator, llvm::gep_type_iterator, llvm::ExecutionContext&)': /home/ggreif/llvm/lib/ExecutionEngine/Interpreter/Execution.cpp:798: warning: 'Idx' might be used uninitialized in this function 7) /home/ggreif/llvm/lib/Target/MSIL/MSILWriter.cpp: In member function `unsigned int <unnamed>::MSILWriter::getBitWidth(const llvm::Type*)': /home/ggreif/llvm/lib/Target/MSIL/MSILWriter.cpp:1449: warning: control reaches end of non-void function /home/ggreif/llvm/lib/Target/MSIL/MSILWriter.cpp: In member function `std::string <un...

...re doing variadic calls, not casting > variadic function to definite ones. I think you can construct CallSite > and then iterate over the arguments grabbing their types and construct > function type after that. > So what do you think about that: // CallSites have equal signatures bool MSILWriter::cmpCallSite(CallSite A, CallSite B) { return (getCallSiteFType(A)==getCallSiteFType(B) && A.getAttributes()==B.getAttributes()); } // Comparision for std::lower_bound used in MSILWriter::printExternals() bool MSILWriter::compareCallSite(CallSite A, CallSite B) { return getCallSi...

Hi, Artur > // CallSites have equal signatures > bool MSILWriter::cmpCallSite(CallSite A, CallSite B) { >   return (getCallSiteFType(A)==getCallSiteFType(B) && >     A.getAttributes()==B.getAttributes()); > } As it is impossible to honour argument attributes in MSIL I don't see why you should compare attributes. You seems to have the same...

...am trying to use llvm to translate ftp.c(a file of wget-1.11.2.tar.bz2 ) to msil. But it shows errors like: [dayin at localhost src]$ llvm-gcc -emit-llvm ftp.c -c -o ftp.bc [dayin at localhost src]$ llc ftp.bc -march=msil -o ftp.s Intrinsic ID = 32 llc: /home/dayin/llvm/llvm-2.2/lib/Target/MSIL/MSILWriter.cpp:802: void <unnamed>::MSILWriter::printIntrinsicCall(const llvm::IntrinsicInst*): Assertion `0 && "Invalid intrinsic function"' failed. llc((anonymous namespace)::PrintStackTrace()+0x15)[0x8759049] /lib/tls/libc.so.6(abort+0xe9)[0x493279] /lib/tls/libc.so.6(__ass...

Hi, Artur > The interesting for me part of the CallInst is printf(i8* noalias %0, i32 > 123). > I was diging in doxygen documentation but I really can't see the easy way to > compare those instructions and again finish with reinvented (but working) > wheel ;). Ah, sorry. I missed that you're doing variadic calls, not casting variadic function to definite ones. I think you

Hello, > So, looking for type of callee (not result, but function type!) you'll > obtain the > real "signature" of callee and if you'll strip all pointer cast you'll > obtain the "declaration" (=variadic) type of the callee. Maybe I misunderstood something but I just get the variadic declaration not the real "signature", like this: const

Hi, Artur Minor comments: > +// Comparision for std::lower_bound used in > MSILWriter::printExternals() > +static bool CompareInstructions(Instruction *A,Instruction *B) > +{ Put brace on the same line as function def. > + if ( !F->use_empty() ) // Print only if used > + { Likewise. Plus use "if (foo)" instead of "if ( foo )". Al...

...ectionDAGISel.h (+3 -1) include/llvm/CodeGen/AsmPrinter.h (+4) lib/CodeGen/LLVMTargetMachine.cpp (+23 -4) lib/CodeGen/AsmPrinter.cpp (+19) lib/CodeGen/SelectionDAG/SelectionDAGISel.cpp (+36 -8) lib/CodeGen/README.txt (+5) lib/Target/CBackend/CBackend.cpp (+3 -1) lib/Target/MSIL/MSILWriter.cpp (+3 -1) Second pass at integrating Collector with the compiler. In general, designating the frametable algorithm on a function-by-function basis was beneficial to the implementation. One thing that sticks in my craw is that Collector and TargetMachine still have no way of verifying th...

Hello > What does these mean? The bytecode contains call to intrinsic, which is not supported by by MSIL backend. The only intrinsics currently supported 'natively' are vastart, vaend, vacopy. You might want to extend MSILWriter to use default intrinsic lowering mechanism, however, don't expect, that you'll have something workable - in general, you cannot just grab .c file, translate it with llvm-gcc to .bc and use MSIL writer - you will still need implementations of bunch of stuff, which are in gcc runtime (e.g....

Anton Korobeynikov wrote: > Hi, Artur > > >> I'm working on that backend now, so probably I'll send some more patches >> soon. I'd be grateful if you could give me some suggestions how to add >> some test for that backend to the test-suite. On Linux the output code >> could be run on Mono and compared with outputs for other backends but >>