search for: assemblywriter

Hey everyone, I'm currently trying to figure out a method for providing a unique identification of an llvm::Instruction that is consistent with the output of an AssemblyWriter. Obviously this is easy for named instructions: In this case the identification is the name itself, but I'd like to have the same thing for unnamed instructions. If I understand the code in AssemblyWriter.cpp correctly, AssemblyWriter uses SlotTracker to keep track of the numbers used for u...

...1401e80, > onlyNamed=false) at TypeFinder.cpp:38 > frame #11: 0x00000001001a97c9 dump`(anonymous > namespace)::TypePrinting::incorporateTypes(this=0x00007ffeefbff530, > M=0x0000000101401e80) at AsmWriter.cpp:491 > frame #12: 0x00000001001a964f dump`(anonymous > namespace)::AssemblyWriter::AssemblyWriter(this=0x00007ffeefbff510, > o=0x00007ffeefbff3f8, Mac=0x00007ffeefbff438, M=0x0000000101401e80, > AAW=0x0000000000000000, IsForDebug=true, ShouldPreserveUseListOrder=false) > at AsmWriter.cpp:2210 > frame #13: 0x000000010019ce22 dump`(anonymous > namespace)::Assemb...

...from the module: 511 GV->eraseFromParent(); (gdb) p GV->dump() ; Function Attrs: ssp uwtable define i32 @_Z1fv() #2 { entry: %call = call i32 (i8*, ...)* @printf(i8* getelementptr inbounds ([21 x i8]* @.str1, i32 0, i32 0)) ret i32 0 } (gdb) n 513 } (gdb) br llvm::AssemblyWriter::printModule(llvm::Module const*) (gdb) p m_CurTransaction->getModule()->dump() llvm::AssemblyWriter::printGlobal (this=0x7fff5fbfe850, GV=0x107274058) at /Users/vvassilev/workspace/root/interpreter/llvm/src/lib/IR/AsmWriter.cpp:1444 1444 if (GV->isMaterializable()) (gdb) p GV->u...

...> (gdb) p GV->dump() > > ; Function Attrs: ssp uwtable > define i32 @_Z1fv() #2 { > entry: > %call = call i32 (i8*, ...)* @printf(i8* getelementptr inbounds ([21 x > i8]* @.str1, i32 0, i32 0)) > ret i32 0 > } > > (gdb) n > 513 } > (gdb) br llvm::AssemblyWriter::printModule(llvm::Module const*) > (gdb) p m_CurTransaction->getModule()->dump() > llvm::AssemblyWriter::printGlobal (this=0x7fff5fbfe850, GV=0x107274058) at > /Users/vvassilev/workspace/root/interpreter/llvm/src/lib/IR/AsmWriter.cpp:1444 > 1444 if (GV->isMaterializable()...

...I am writing a new transformation (Basic block pass). In the "\llvm-2.5\lib\VMCore\AsmWriter.cpp " file there are some of function i want to use. What do i need to add to the transformation code, so i will be able to use those functions? I tried to use a function and got this error : 'AssemblyWriter' was not declared in this scope. Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090523/cc964bc0/attachment.html>

...polly::ScopDetection::DetectionContext&) const () The detailed backtrace of "isValidMemoryAccess" is: #0 0x0907b780 in llvm::TypeFinder::run(llvm::Module const&, bool) () #1 0x08f76ebe in llvm::TypePrinting::incorporateTypes(llvm::Module const&) () #2 0x08f76fc9 in llvm::AssemblyWriter::init() () #3 0x08f77176 in llvm::AssemblyWriter::AssemblyWriter(llvm::formatted_raw_ostream&, llvm::SlotTracker&, llvm::Module const*, llvm::AssemblyAnnotationWriter*) () #4 0x08f79d1a in llvm::Value::print(llvm::raw_ostream&, llvm::AssemblyAnnotationWriter*) const () #5 0xb7c1d044...

...ionContext&) const () > > The detailed backtrace of "isValidMemoryAccess" is: > #0 0x0907b780 in llvm::TypeFinder::run(llvm::Module const&, bool) () > #1 0x08f76ebe in llvm::TypePrinting::incorporateTypes(llvm::Module const&) > () > #2 0x08f76fc9 in llvm::AssemblyWriter::init() () > #3 0x08f77176 in > llvm::AssemblyWriter::AssemblyWriter(llvm::formatted_raw_ostream&, > llvm::SlotTracker&, llvm::Module const*, llvm::AssemblyAnnotationWriter*) () > #4 0x08f79d1a in llvm::Value::print(llvm::raw_ostream&, > llvm::AssemblyAnnotationWriter*)...

On 23 July 2013 16:50, Tobias Grosser <tobias at grosser.es> wrote: > On 07/22/2013 11:58 PM, Star Tan wrote: > >> Hi Tobias, >> >> >> I have attached a patch file to optimize string operations in >> Polly-Detect pass. >> In this patch file, I put most of long string operations in the condition >> variable of "PollyViewMode" or in

...ter -I llvm\lib\Target\X86 -o tablegen_includes\X86GenATTAsmWriter. inc llvm\lib\Target\X86\X86.td llvm\lib\Target\X86\X86InstrInfo.td llvm\lib\Target\X86\X86RegisterInfo.td llvm\lib\Targe t\Target.td d:/home/arathorn/sandbox/llvm/tblgen.exe: Record 'X86' does not have a field named 'AssemblyWriter! d:/home/arathorn/sandbox/llvm/tblgen.exe -gen-instr-enums -I llvm\lib\Target\X86 -o tablegen_includes\X86GenInstrNames.i nc llvm\lib\Target\X86\X86.td llvm\lib\Target\X86\X86InstrInfo.td llvm\lib\Target\X86\X86RegisterInfo.td llvm\lib\Target \Target.td d:/home/arathorn/sandbox/llvm/tblgen.exe:...

I fell over this issue yesterday myself with lots of asserts being thrown. I think the issue is in lib/IR/AsmWriter.cpp:1618 in the function AssemblyWriter::printFunction(const Function *F) Looking at the code I think the 2nd for loop should be preceded by the test ... if (Idx < AS.getNumSlots()) Not sure why it doesn't fail on other platforms as it looks like it should be a genuine issue on all platform. That change significantly reduce...

Hi. I want to do a cutomized points-to analysis on IR. Suppose that we have: *%91 = bitcast i8* %90 to %struct.demux_packet*, !dbg !2688* I want to store sth similar to %91 -> target of %90, which records the target of pointer named %91. How can I access the names (Here, %90 and %91)? I know that I can put the whole line for an instruction into a string, using the following code: *string str;*

Hi As requested from Paolo, I've sent him the tablegen tool. The tool is able to compile the td files (given in the makefile) on windows without any complaints. Henrik >From: Paolo Invernizzi <arathorn at fastwebnet.it> >Date: Thu, 7 Oct 2004 14:27:11 +0200 > >Hi Henrik, > >As you may remember, I'm trying to use the LLVM core tools under Visual >Studio.

...ction Attrs: ssp uwtable >> define i32 @_Z1fv() #2 { >> entry: >> %call = call i32 (i8*, ...)* @printf(i8* getelementptr inbounds ([21 x >> i8]* @.str1, i32 0, i32 0)) >> ret i32 0 >> } >> >> (gdb) n >> 513 } >> (gdb) br llvm::AssemblyWriter::printModule(llvm::Module const*) >> (gdb) p m_CurTransaction->getModule()->dump() >> llvm::AssemblyWriter::printGlobal (this=0x7fff5fbfe850, GV=0x107274058) at >> /Users/vvassilev/workspace/root/interpreter/llvm/src/lib/IR/AsmWriter.cpp:1444 >> 1444 if (GV->is...

...are either debug-only (writing to std::cerr), or for JIT, or for ELF (which is not used anywhere, BTW). Ideally, I'd like to create my own MachineCodeEmitter derived class, load it into llc with the -load option, and then have new option for 'llc' that will use MachineCodeEmitter, not AssemblyWriter, to generate the file. The reason I'm trying to do this is that the target does not have an assembler, and does not need it, and so designing an assembler syntax just for the sake of code generation does not seem right. Any suggestions how I should proceed? Thanks, Volodya

...polly::ScopDetection::DetectionContext&) const () The detailed backtrace of "isValidMemoryAccess" is: #0 0x0907b780 in llvm::TypeFinder::run(llvm::Module const&, bool) () #1 0x08f76ebe in llvm::TypePrinting::incorporateTypes(llvm::Module const&) () #2 0x08f76fc9 in llvm::AssemblyWriter::init() () #3 0x08f77176 in llvm::AssemblyWriter::AssemblyWriter(llvm::formatted_raw_ostream&, llvm::SlotTracker&, llvm::Module const*, llvm::AssemblyAnnotationWriter*) () #4 0x08f79d1a in llvm::Value::print(llvm::raw_ostream&, llvm::AssemblyAnnotationWriter*) const () #5 0xb7c1d044...

...) >> >> The detailed backtrace of "isValidMemoryAccess" is: >> #0 0x0907b780 in llvm::TypeFinder::run(llvm::Module const&, bool) () >> #1 0x08f76ebe in llvm::TypePrinting::incorporateTypes(llvm::Module const&) >> () >> #2 0x08f76fc9 in llvm::AssemblyWriter::init() () >> #3 0x08f77176 in >> llvm::AssemblyWriter::AssemblyWriter(llvm::formatted_raw_ostream&, >> llvm::SlotTracker&, llvm::Module const*, llvm::AssemblyAnnotationWriter*) () >> #4 0x08f79d1a in llvm::Value::print(llvm::raw_ostream&, >> llvm::Assemb...

...nces(); } } for(BasicBlock::iterator bi= bbp->getFirstNonPHI(),ie=bbp->end();bi!=ie;++bi){ if((*bi).getNumOperands()==0) {(*bi).eraseFromParent();} } -------------------------------------------------------------------------------------------------------------- Error: (gdb) bt #0 llvm::AssemblyWriter::printInstruction (this=0xbfa1a75c, I=@0x877b488) at AsmWriter.cpp:1378 #1 0x085b2ece in llvm::AssemblyWriter::write (this=0xbfa1a75c, I=0x877b488) at AsmWriter.cpp:741 #2 0x085adb0f in llvm::Instruction::print (this=0x877b488, o=@0x8794f48, AAW=0x0) at AsmWriter.cpp:1482 #3 0x085b5bf2 in llv...

...var names > as: > > /* temporary 1 */ = tail call i32 @bar(i32 %a) > > (assuming LLVM syntax would have stream-type comments besides line-type > ";"). > > Printing a comment there is pretty useless. It's probably historical. It should be pretty easy to change AssemblyWriter::printBasicBlock in lib/IR/AsmWriter.cpp to print out a "unnamed" name for the BB, but the hard part will be to ensure that the new policy will properly round-trip (i.e., can be parsed back; even in the presence of user-defined names). Also, we like to keep the textual IR as compatible as...

...erences();} } for(BasicBlock::iterator bi= bbp->getFirstNonPHI(),ie=bbp->end();bi!=ie;++bi){ if((*bi).getNumOperands()==0) {(*bi).eraseFromParent();} } -------------------------------------------------------------------------------------------------------------- Error: (gdb) bt #0 llvm::AssemblyWriter::printInstruction (this=0xbfa1a75c, I=@0x877b488) at AsmWriter.cpp:1378 #1 0x085b2ece in llvm::AssemblyWriter::write (this=0xbfa1a75c, I=0x877b488) at AsmWriter.cpp:741 #2 0x085adb0f in llvm::Instruction::print (this=0x877b488, o=@0x8794f48, AAW=0x0) at AsmWriter.cpp:1482 #3 0x085b5bf2 in llvm::...

On 07/14/2013 08:05 AM, Star Tan wrote: > I have found that the extremely expensive compile-time overhead comes from the string buffer operation for "INVALID" MACRO in the polly-detect pass. > Attached is a hack patch file that simply remove the string buffer operation. This patch file can significantly reduce compile-time overhead when compiling big source code. For example, for