search for: asmwriter

...ines-hidden -I/local/scratch/llvm-tmp/build/lib/VMCore -I/local/scratch/llvm-tmp/llvm/lib/VMCore -I/local/scratch/llvm-tmp/build/include -I/local/scratch/llvm-tmp/llvm/include -Wall -W -Wno-unused-parameter -Wwrite-strings -pedantic -Wno-long-long -fno-exceptions -o CMakeFiles/LLVMCore.dir/AsmWriter.cpp.o -c /local/scratch/llvm-tmp/llvm/lib/VMCore/AsmWriter.cpp In file included from /local/scratch/llvm-tmp/llvm/lib/VMCore/AsmWriter.cpp:27:0: /local/scratch/llvm-tmp/llvm/include/llvm/Operator.h:38:3: error: deleted function 'virtual llvm::Operator::~Operator()' In file included from...

Ryan Taylor wrote: > Nick, > > Unfortunately this doesn't answer my question I don't think. It > seems that -instnamer, as you mention, names the instructions but still > does not name the local variables. What other local variables are you referring to? When AsmWriter prints "%y = add i32 %x, 1", the name of that add instruction is "y" and "x" is the name of another instruction or argument. If it has no name, the AsmWriter emits a number ("%0"), by counting from the top. The only other locals could be function argument...

Hi guys Is some one able to explain me, why these errors emerge: gmake[2]: Entering directory `/usr/local/src/llvm/lib/VMCore' Compiling AsmWriter.cpp AsmWriter.cpp: In function `void WriteConstantInt(std::ostream&, const llvm::Constant*, bool, std::map<const llvm::Type*, std::string, std::less<const llvm::Type*>, std::allocator<std::pair<const llvm::Type* const, std::string> > >&, llvm::SlotCalculator...

...olTable.h" (frontend) resolved this. > > Ok. This is now fixed on the release branch. Thanks! The strange thing is that the configure process defines: #define HAVE_STDINT_H 1 However, without literally including stdint.h (which should be avoided as Reid mentioned) the compilation of AsmWriter.cpp goes wrong, although stdint.h, llvm/Support/DataTypes.h and inttypes.h are all mentioned in AsmWriter.d: if g++ -I/home/bram/workspace/svn/aspicere2/trunk/llvm-build/lib/ VMCore -I/home/bram/workspace/svn/aspicere2/trunk/llvm/lib/VMCore -I/ home/bram/workspace/svn/aspicere2/trunk/llvm-bu...

...atch/llvm-tmp/**build/lib/VMCore > -I/local/scratch/llvm-tmp/**llvm/lib/VMCore -I/local/scratch/llvm-tmp/**build/include > -I/local/scratch/llvm-tmp/**llvm/include -Wall -W > -Wno-unused-parameter -Wwrite-strings -pedantic -Wno-long-long > -fno-exceptions -o CMakeFiles/LLVMCore.dir/**AsmWriter.cpp.o -c > /local/scratch/llvm-tmp/llvm/**lib/VMCore/AsmWriter.cpp > In file included from /local/scratch/llvm-tmp/llvm/** > lib/VMCore/AsmWriter.cpp:27:0: > /local/scratch/llvm-tmp/llvm/**include/llvm/Operator.h:38:3: error: > deleted function 'virtual llvm::Operator::~Operator(...

Nick, Unfortunately this doesn't answer my question I don't think. It seems that -instnamer, as you mention, names the instructions but still does not name the local variables. So there really is no way to do this shy of creating (or basically copying) the API from AsmWriter (seems very dedundant to me)? This seems like a large failing? On Fri, Oct 21, 2011 at 7:03 PM, Nick Lewycky <nicholas at mxc.ca> wrote: > Ryan Taylor wrote: > >> It looks like the AsmWriter is generating the local variables (SlotNum)s >> on the fly in that file (AsmWriter...

It looks like the AsmWriter is generating the local variables (SlotNum)s on the fly in that file (AsmWriter.cpp), so is there any way at all to get this information from the operation itself, via Instruction, Value or Type? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.o...

...0x00000001004bad34 > dump`llvm::TypeFinder::run(this=0x00007ffeefbff530, M=0x0000000101401e80, > 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 As...

Hi I am not a good programmer but for my project i have to use llvm to generate CFG for c programs where i have a mapping from IR instruction in CFG to their respective c instruction. After surfing a in source of llvm i did the following change in printInstruction() function in llvm/lib/VMCore/AsmWriter.cpp file. .....void AssemblyWriter::printInstruction(const Instruction &I) { if (AnnotationWriter) AnnotationWriter->emitInstructionAnnot(&I, Out); // Print out indentation for an instruction. Out << " "; if (MDNode *N = I.getMetadata("dbg")) {...

...c_ostream to use. Why? > >It appears that your libstdc++ does not support insertion of 64-bit >integers into iostreams. Did I mention that you should try cygwin? ;-) > >-Chris > > > > gmake[2]: Entering directory `/usr/local/src/llvm/lib/VMCore' > > Compiling AsmWriter.cpp > > AsmWriter.cpp: In function `void WriteConstantInt(std::ostream&, const > > llvm::Constant*, bool, std::map<const llvm::Type*, std::string, > > std::less<const llvm::Type*>, std::allocator<std::pair<const >llvm::Type* > > const, std::st...

...or is missing. You said that you are using GCC on internix. Is it possible that when you configured/built gcc that it didn't find 64-bit integer support and disabled it or something? I really no nothing about internix so all I can do is speculate. Sorry. -Chris > > > Compiling AsmWriter.cpp > > > AsmWriter.cpp: In function `void WriteConstantInt(std::ostream&, const > > > llvm::Constant*, bool, std::map<const llvm::Type*, std::string, > > > std::less<const llvm::Type*>, std::allocator<std::pair<const > >llvm::Type* > &gt...

...ffect is actually much *more* prominent than I first made it out to be. This is just one data point, of course, but I get an easily noticable slowdown with every Pure script I tried. In fact it's so much slower that I consider it unusable. I'm at a loss here. I'd have to debug the LLVM asmwriter code to see where exactly the bottleneck is. I haven't done that yet, but I ruled out an issue with the raw_ostream buffer sizes by trying different sizes from 256 bytes up to 64K; it doesn't change the results very much. So my question to fellow frontend developers is: Has anyone else see...

> On Slackware 10.2 (GCC 3.3.6), I got an error during a debug build with the > header files using uintptr_t (not recognised as a type). Putting "#include > <stdint.h>" in include/llvm/BasicBlock.h (llvm) and in > "include/llvm/ValueSymbolTable.h" (frontend) resolved this. Ok. This is now fixed on the release branch. Thanks! > Also, I got linking

...sible that when you configured/built gcc that it >>didn't find 64-bit integer support and disabled it or something? >> >>I really no nothing about internix so all I can do is speculate. Sorry. >> >>-Chris >> >> >> >>> > > Compiling AsmWriter.cpp >>> > > AsmWriter.cpp: In function `void WriteConstantInt(std::ostream&, >>>const >>> > > llvm::Constant*, bool, std::map<const llvm::Type*, std::string, >>> > > std::less<const llvm::Type*>, std::allocator<std::pair&l...

...tarted.html#brokengcc Please be warned as your get miss compiles and things will do strange `stuff`. As can be seen here, the reverse is true for both the GNU binutils and XPG4 versions of `nm' : -bash-3.2$ /usr/xpg4/bin/nm -p -u `find . -name libLLVMCore.a` | head ./Debug/lib/libLLVMCore.a[AsmWriter.o]: 0000000000 U __assert 0000000000 U __clzdi2 0000000000 U __udivdi3 0000000000 U __umoddi3 0000000000 U _GLOBAL_OFFSET_TABLE_ 0000000000 U _ZdaPv 0000000000 U _ZdlPv -bash-3.2$ /usr/bin/nm -p -u `find . -name libLLVMCore.a` | head ./Debug/lib/libLLVMCore.a[AsmWriter.o]: __assert __clzd...

...t than I first made it > out > to be. This is just one data point, of course, but I get an easily > noticable slowdown with every Pure script I tried. In fact it's so > much > slower that I consider it unusable. > > I'm at a loss here. I'd have to debug the LLVM asmwriter code to see > where exactly the bottleneck is. I haven't done that yet, but I ruled > out an issue with the raw_ostream buffer sizes by trying different > sizes > from 256 bytes up to 64K; it doesn't change the results very much. > > So my question to fellow frontend dev...

...gcc that it >>>didn't find 64-bit integer support and disabled it or something? >>> >>>I really no nothing about internix so all I can do is speculate. Sorry. >>> >>>-Chris >>> >>> >>> >>>> > > Compiling AsmWriter.cpp >>>> > > AsmWriter.cpp: In function `void WriteConstantInt(std::ostream&, >>>>const >>>> > > llvm::Constant*, bool, std::map<const llvm::Type*, std::string, >>>> > > std::less<const llvm::Type*>, std::allocato...

...ker up and running. Structurally its a lot like llvm-as. When I run it, I get: Leaked objects found: after running pass 'Function Pass Manager' LLVM Value subclasses leaked: Note that the supposed list of "LLVM Value subclasses leaked" is empty. Its followed up by a SIGSEGV at AsmWriter.cpp:754 presumably because I have a BasicBlock object not assigned to a Function. Is the message above attempting to tell me this? What I can't figure out is where the message comes from and why. Reid. -------------- next part -------------- A non-text attachment was scrubbed... Name: sig...

Dan Gohman wrote: > One other question the occurs to me: is Pure dumping the whole Module > at once, or is it manually writing out the IR in pieces? Well, you hit the nail on the head with that one. ;-) In fact, I just had the same idea. So, instead of selecting and emitting individual globals and functions on the fly, I rewrote the .ll writer in Pure so that it just erases unwanted stuff

On Aug 24, 2009, at 3:05 PM, Ivo wrote: > On Monday 24 August 2009 23:27, Albert Graef wrote: >> Thank you also for the hint about bitcode reading/writing. I'm >> aware of >> this, but I actually prefer the .ll output because it's human- >> readable, >> which is great for debugging purposes. I might add a bitcode writer >> some >> time,