similar to: [LLVMdev] Memory leaks in LLVM

I am writing an interprocedural compiler pass. Because the passneeds information from a FunctionPass, e.g., the post-dominance frontier (PDF), and because a ModulePass is not permitted to require a FunctionPass, I am forced to make my pass a FunctionPass and do majority of its work in the doFinalization() method. When I run "opt -mypass -verify -o code2.bc code1.bc" I get no

On Wed, 21 Feb 2007, Ryan M. Lefever wrote: > I am writing an interprocedural compiler pass. Because the passneeds > information from a FunctionPass, e.g., the post-dominance frontier > (PDF), and because a ModulePass is not permitted to require a > FunctionPass, I am forced to make my pass a FunctionPass and do majority > of its work in the doFinalization() method. ok > When

Ryan, This looks like a bug. Could you file it, please? Reid. On Thu, 2007-02-22 at 19:47 -0600, Ryan M. Lefever wrote: > I have a compiler transform that I have been working on that produces > bytecode that passes the verifier. However, when I try to read that > bytecode back in, I get the assertion failure below. > > llvm::BytecodeReader::ParseConstantPoolValue(unsigned

I have a compiler transform that I have been working on that produces bytecode that passes the verifier. However, when I try to read that bytecode back in, I get the assertion failure below. llvm::BytecodeReader::ParseConstantPoolValue(unsigned int): Assertion `(!isa<Constant>(Result) || !cast<Constant>(Result)->isNullValue()) || !hasImplicitNull(TypeID) &&

I am still diagnosing the cause of the assertion failure and will submit a bug when I better understand the problem. Reid Spencer wrote: > Ryan, > > This looks like a bug. Could you file it, please? > > Reid. > > On Thu, 2007-02-22 at 19:47 -0600, Ryan M. Lefever wrote: > >>I have a compiler transform that I have been working on that produces >>bytecode

I think I misread the doxygen. verifyFunction & verifyModule return false if no errors are detected. However, my question now becomes why does the code produced by my transform pass verification, but it causes an assertion failure in the byte reader when it (the code produced by my transform) is passed to another invocation of opt? Ryan M. Lefever wrote: > I also tried iterating

I also tried iterating through the functions of the module and calling verifyFunction(), which also returns false, but does not cause an abort or report anything to stderr about what caused the verification to fail. From the doxygen for verifyFunction() and verifyModule(), it seems like they both should print information to stderr if the verification fails and should abort opt if

I followed what you said and called verifyModule() with the AbortProcessAction option. verifyModule() returns false, but does not abort and does not print out any information about what caused the verification to fail. Chris Lattner wrote: > On Wed, 21 Feb 2007, Ryan M. Lefever wrote: >> I am writing an interprocedural compiler pass. Because the passneeds >> information from a

Jeff, Thanks for reporting this. I had no idea ::read was being used in ReaderWrappers. I have re-implemented it using istream facilities. This should be much more portable. Please try again and let me know if its better. Thanks, Reid. On Mon, 2004-12-20 at 22:31, Jeff Cohen wrote: > Primitive Unix I/O should not be used outside of lib/System: > >

On Wed, 2006-04-26 at 16:32 -0500, Chris Lattner wrote: > I still don't follow. Having annotations on the IR is *exactly* > equivalant to having a map from IR objects to the things you want to > annotate them with. > > Why isn't this just as acceptable (and problematic) as annotations? Because LLVM doesn't store that map, someone else has to. Furthermore, LLVM

Primitive Unix I/O should not be used outside of lib/System: c:\llvm\lib\Bytecode\Reader\ReaderWrappers.cpp(140) : error C2039: 'read' : is not a member of 'operator``global namespace'''

Hello, as you might have noticed, there has been no change in the number of fixed bugs/features for quite some time now. The fact is, I''m studying again since October last year and did not have enough time for webgen. However, I did find some time lately and I wanted to let you know what has been done by now. The main motivation behind the next major release (0.4.0) was making webgen

Hi, I get this error: ------------------ Reader.cpp:464: error: `intptr_t' undeclared (first use this function) ------------------ It doesn't seem that you include <stddef.h>, where the intptr_t is declared, in the source file. When I included the header, it compiled without errors. The same error seems to be present for ReaderWrappers.cpp. /Henrik

I'm getting an error when trying to build llvm 2.2's tblgen: llvm[2]: Linking Release executable tblgen (without symbols) /usr/bin/ld: Undefined symbols: llvm::MemoryBuffer::getFileOrSTDIN(char const*, unsigned int, std::basic_string<char, std::char_traits<char>, std::allocator<char> >*, long long) llvm::cl::ParseCommandLineOptions(int, char**, char const*) It's

Bram, I looked over your patch and it looks good. I applied a patch based on yours. The llvm-ld tool now uses the PluginLoader just like the opt tool. It will also run some cleanup passes after the loaded plugins run to ensure cruft is removed. See this patch for details: http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20060814/036882.html Thanks for the patch! And, yes, you are on

Hi Óscar, On 22/11/12 09:41, Óscar Fuentes wrote: > Luba Tang <lubatang at gmail.com> writes: > >> We found `llvm-config --cxxflags' does not have -fno-exceptions -fno-rtti >> when using cmake to build LLVM. >> Does anyone know how to fix it? > > Using -fno-rtti and -fno-exceptions is an internal LLVM policy. There is > no reason to impose it on client

Nick, While enhancing the fink llvm32 packaging to support the polly tool, I ran into a dyld failure when the dragonegg plugin tries to load LLVMPolly.so plugin... dyld: lazy symbol binding failed: fast lazy bind offset out of range (39257, max=7640) in image /sw/lib/gcc4.7/libexec/gcc/x86_64-apple-darwin11.4.2/4.7.2/cc1 dyld: fast lazy bind offset out of range (39257, max=7640) in image

I found 179 more *.{c,cpp,h} files with tabs. Unfortunately, the tabs stops used vary so blindly expanding them messes up alignment in many cases :( Index: examples/BFtoLLVM/BFtoLLVM.cpp Index: include/llvm/AbstractTypeUser.h Index: include/llvm/GlobalVariable.h Index: include/llvm/InstrTypes.h Index: include/llvm/IntrinsicInst.h Index: include/llvm/ADT/PostOrderIterator.h Index:

Duncan Sands <baldrick at free.fr> writes: >> Using -fno-rtti and -fno-exceptions is an internal LLVM policy. There is >> no reason to impose it on client code. > > actually it does impact external code. For example dragonegg does > > #include "llvm/Support/PluginLoader.h" > > This file contains > > // This causes operator= above to be

Jack, Some binary has an initializer which dyld is calling. Somehow the initializer gets to: #4 0x0000000100f3b2c0 in Json::Value::maxUInt () which is calling a function in another dylib for the first time. When you call a function in another dylib, you actually jump through a (lazy) pointer. The pointer initially points to a helper which loads an index parameter specifying which function to