similar to: [LLVMdev] Hit assert(I != ValueMap.end() && "Value not in slotcalculator!") in ValueEnumerator.cpp

Hi Guoliang, > I added a function to a module, but failed to write the bitcode to file > because it hit the: > assert(I != ValueMap.end()&& "Value not in slotcalculator!") does the module pass the verifier after you add the function to it? Ciao, Duncan.

Hello, This is my first post to llvmdev (reading for about a month) so I apologize if I'm not following protocol. I'm writing a Common Lisp compiler using LLVM with the C++ API and I'm experiencing a problem that I have not been able to solve by myself. I'm getting a "Value not in slotcalculator" when I write out bitcode for a module that I generated. It happens the

After cloning a Module with CloneModule, there doesn't seem to be any easy way to convert a Value pointing into the old Module to a Value pointing into the new one. The CloneModule implementation already has to keep such a mapping internally, so I've written a patch that exposes it as a second inout parameter to CloneModule(), with the one param version being a simple wrapper for backward

Hello Everyone, I am trying to create two modules in LLVM, where first module contains the definition of a function, gcd in this example and another module contains a call to this function. My example is based on the following tutorial, with a few changes. http://llvm.org/releases/2.6/docs/tutorial/JITTutorial2.html When I execute the verifier pass on my modules, it complains that the

Hi, I have a question about llvm/ADT/DenseMap.h and llvm/IR/ValueMap.h: When you have a: MapType M; is it safe to do: M[NewKey] = M[OldKey]; or do you need to do it in two steps: auto tmp = M[OldKey]; // ensure the reference to M[OldKey] is copied, before reassigning. M[NewKey] = tmp; // might reallocate aka, will a possible allocation for M[NewKey] invalidate the

I actually ran into an elusive bug with this exact same issue some time ago as well, see https://bugs.llvm.org/show_bug.cgi?id=42065 and https://reviews.llvm.org/D62624. The strange thing about that bug was that it only showed up if built with GCC; Clang dereferenced the right hand side reference before evaluating the left hand side, as long as the value type was as small as the reference

Hi all, Finally I managed to find out a strange problem under Visual C During the link of the HowToUseJIT program, I was always missing some symbols... and I was going crazy testing out different options... At the end, unmangling the differences in what linker was searching and what was present in the libraries, I found that the problem is that we have something like this... Value.h struct

Hi, I am back into working on LLVM now and am having problems with Cygwin builds. Problems with both the 1.9 Release and the CVS on Cygwin... LLVM CVS Release build :- /usr/src/llvm/configure --prefix=/usr/llvm make tools-only ENABLE_OPTIMIZED=1 make[3]: Entering directory `/usr/src/lib/Bytecode/Writer' llvm[3]: Compiling SlotCalculator.cpp for Release build llvm[3]: Compiling

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,

No, Chris, I'm not buying that argument, due to I've tweaked /usr/include/types.h a little bit, so the configuration and compilation of the cfrontend would be correct: /* * 64bit type for BSD compatability */ #ifdef __GNUC__ typedef long long int quad_t; typedef unsigned long long int u_quad_t; typedef long long int int64_t; typedef unsigned long long int u_int64_t;

Hi, I want to pass parameter to a analysis pass. My pass need to use some result from some other tools. I can hard code a file name into my pass, and let my pass read input there, but what if I do not want the file name to be hard coded? Is it possible to do that? If yes, where can I find some documentation about it? Thanks, Guoliang

On Thu, 26 Sep 2019, David Blaikie wrote: > I'd be surprised if Clang or GCC's behavior here varied depending on the > size of anything, but maybe? > > In any case, C++17 or so requires the RHS to be evaluated before the LHS for > assignments - so this is now /always/ wrong, not just unspecified (which, I > guess, also always wrong... just sometimes accidentally right)

Hi all, I'm rather new to LLVM and intend to dive into partial evaluation with LLVM. I tried to run the example from http://llvm.org/devmtg/2008-08-23/llvm_partial.pdf, which worked after some adaptations, which were necessary, because LLVM evolved since the slides were made. However, I also tried to get the same example running as an optimization pass following the instructions in

Hello Visual Studio is complaining about the mix of struct and class. 2>C:\dev\llvm\include\llvm/ADT/ValueMap.h(202) : warning C4099: 'llvm::DenseMapInfo<llvm::ValueMapCallbackVH<KeyT,ValueT,Config,ValueInfoT>>' : type name first seen using 'struct' now seen using 'class' 2> C:\dev\llvm\include\llvm/ADT/ValueMap.h(251) : see reference to class

On Wed, 7 Jul 2004, Henrik Bach wrote: > This tweak seems to work. > > As far as I can see, correct me if I'm wrong, it is the compiler, that can't > figure out which std::basic_ostream to use. Why? What I'm saying is that it appears that your implementation of operator<< is not functional or is missing. You said that you are using GCC on internix. Is it possible

Hi, I found the following at http://llvm.org/docs/SourceLevelDebugging.html#ccxx_frontend: if (MDNode *N = I->getMetadata("dbg")) { // Here I is an LLVM instruction DILocation Loc(N); // DILocation is in DebugInfo.h unsigned Line = Loc.getLineNumber(); StringRef File = Loc.getFilename(); StringRef Dir = Loc.getDirectory(); } Does this also

Hi, I would like to get the whole program bitcode with debug information in it. I tried to use CFLAGS = "-O4 -g", but it ends with the following error: collect2: ld terminated with signal 6 [Aborted] Unknown constant! UNREACHABLE executed at /local.toadette/aliang/fixing/llvm-2.7/llvm-2.7/lib/Bitcode/Writer/BitcodeWriter.cpp:895! What is the right way to get a whole program bitcode

Hi there, I checked out the latest code from the repository, and wanna use the gold plugin, but I got the following: libLLVMgold.so: could not load plugin library Do you know why this is happening? Also I noticed the name of the library is changed to LLVMgold.so, and I just renamed it to libLLVMgold.so when I copied it. Is this the right thing to do? Thanks, Guoliang

Hi, While attempting to build the LLVM code from CVS today using gcc 4.1, I encountered the following error. Any idea how to proceed with the build? llvm[2]: Linking Debug executable llvm-as /home/ll/programs/source/scm/cvs/llvm/Debug/lib/libLLVMAsmParser.a(llvmAsmParser.o): In function `__static_initialization_and_destruction_0':

Hi, I'm gonna try to give some feedback, but I have only been working with LLVM for a few days, so don't take what I'm saying without verifying :-) > BasicBlock *ProgSlicer::CloneBasicBlock(const BasicBlock *BB, > DenseMap<const Value*, Value*> &ValueMap, > const char *NameSuffix, Function *F) { > > BasicBlock