similar to: [help] Kaleidoscope build fails after llvm-3.8

Greetings, I am having trouble getting the Kaleidoscope example to build from tutorial #3 on Mac OS X 10.6.2. I didn't have too much trouble getting llvm-2.6 and llvm-gcc-frontend to build. Thanks for the help. Here are the steps I followed: Environment variables for build export LLVMOBJDIR=/opt/llvm export TARGETOPTIONS='--with-arch=nocona --with-tune=generic' export

Hi, I am trying to use some LLVM API in my C++ code, and I end up getting linker errors. I am working on Apple MacOSX Lion. Using g++ for the compile. It is the CreateGlobalStringPtr which is throwing the error. This is LLVM 3.0. Here's the codeI am trying to use some LLVM API in my C++ code, and I end up getting linker errors. I am working on Apple MacOSX Lion. Using g++ for the compile. It

Hi llvm-dev, Our code base has a ancient copy of llvm (ver 3.5.1), and it uses the LLVM code gen for some domain-specific language. The previous dev left a global lock around the usage of LLVM code gen stating that because LLVM code gen can only be accessed single-threaded it needs to be protected with this global lock. But now this lock has caused some perf issues as we pretty much lose

Thank you Johannes, I looked it up and it seems that we're creating one LLVMContext per compilation "unit", not sure if that matters. i.e. there's no single globally shared LLVMContext object. Is LLVMContext *the* concurrency isolation (or unit) here? On Wed, Apr 3, 2019 at 6:34 PM Doerfert, Johannes <jdoerfert at anl.gov> wrote: > Do you use one llvm context or one

Probably your g++ compiles x86_64 binary by default, but i686 dylib is supplied? Try: g++ -m32 e.cpp /Developer/Platforms/iPhoneOS.platform/Developer/usr/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin10/4.2.1/libllvmgcc.dylib - D. 2012/1/22 Arpan Sen <arpansen at gmail.com>: > Hi, > > I am trying to use some LLVM API in my C++ code, and I end up getting linker > errors. I am

Hi I get huge memory leaks using LLVM IRBuilder (trunk version) Basically I recreate a function over and over again, and pretty sure that my code doesn't cause the leak while(true) { Function *fn = module->getFunction(name); if (fn) fn->eraseFromParent(); fn = cast<Function>(module->getOrInsertFunction(name, fnType)); fillFunction(fn); //Fill function with

Hi, I'm having a hard time finding an answer to what I assume is a very basic idea. I'm trying to produce this llvm code using the LLVM api: %myString = alloca [13 x i8], i32 13 store [13 x i8] c"Hello world.\00", [13 x i8]* %myString %tmp1 = getelementptr [13 x i8]* %myString, i32 0, i32 0 %tmp2 = call i32 (i8*, ...)* @printf( i8* %tmp1 ) nounwind A simple Hello

[ Original posting see [1] ] >From [1]: ... Added: llvm/tags/RELEASE_380/rc3/ (props changed) - copied from r261685, llvm/branches/release_38/ ... The LLVM Git repositories have no "rc3" tag in "release_38" branch (as an example llvm.git#release_38 see [2]). Who is responsible for that or maybe better... can you activate the responsible(s)? Helpful is to add

Hi Jeffrey, Listed below the Full valgrind report (using latest revision r99309) The program creates many thousands of instructions and values as you can see from the report below ==20504== Memcheck, a memory error detector ==20504== Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al. ==20504== Using Valgrind-3.5.0-Debian and LibVEX; rerun with -h for copyright info ==20504==

On 26 June 2016 at 13:31, Anton Korobeynikov via llvm-dev <llvm-dev at lists.llvm.org> wrote: > What you're probably missing is that 3.8.1 is made in release_38 > branch. So, everything is there and already mirrored. > > Source tarballs will be available upon the release. Which are just coming, now that final has been tested successfully. :) They'll be announced in the

Hi, I have problem with IRBuilderBase::InsertPointGuard class that simply does not work in the release build of my project. The class does not restore the IRBuilder's insert point correctly when NDEBUG macro is set. It happens on OSX system only, trunk version of the LLVM built with brew. I suspect it is the ABI problem. InsertPointGuard uses AssertingVT for debug builds. LLDB gets confused

Hello, In one of the loop transformations I am developing, I need to convert eq and neq loop latch condition into less than or greater than depending on the control flow. The problem is that CmpInst::ICMP_EQ and CmpInst::ICMP_NE are neither signed nor unsigned in LLVM. Also, I did not find a way to find out if the integer operands of the CmpInst are signed or unsigned. Apparently, LLVM does

I am compiling and linking Kaleidoscope sample from 2 to 7 with Code::Blocks, where I have add to compiler settings: `llvm-config --cxxflags` and to linker settings: `llvm-config --ldflags --system-libs --libs core orcjit native` In 2 to 7 is OK, but sample 8 has errors: ||=== Build: Debug in Chapter8 (compiler: LLVM Clang Compiler) ===| obj/Debug/toy.o||In function

I’ve been developing an optimization pass that uses the address space attribute (__attribute__((address_space(200))) to indicate different kinds of pointers to be treated differently (I’m making them be pointers to a “global” address space as in UPC). However, I’ve hit a snag in the frontend code generator: if I try to make a method call on a pointer with a custom address space, the frontend

Git tags and SVN tags are completely different beasts (git tag is simply a "second name" attached to revision, while on svn the tag could be arbitrary different). There is no way to automate the process - in general svn tag might not correspond (by contents) to any other revision in the repository. The only way to somehow emulate svn tags on git is to create a separate branch on each

I.e., I see this when I run `git fetch`: ``` $ git fetch -v llvm.org From http://llvm.org/git/llvm = [up to date] master -> llvm.org/master = [up to date] release_1 -> llvm.org/release_1 = [up to date] release_16 -> llvm.org/release_16 = [up to date] release_20 -> llvm.org/release_20 = [up to date] release_21 -> llvm.org/release_21 = [up to date]

On 02/03/2016 11:06 AM, Tobias Grosser wrote: > On 02/03/2016 04:46 PM, Frank Winter via llvm-dev wrote: >> >> >> On 02/03/2016 10:41 AM, Tobias Grosser wrote: >>> On 02/03/2016 04:37 PM, Frank Winter wrote: >>>> Hi Tobias, >>>> >>>> I tried to invoke other passes and none of them are available, e.g.: >>>>

On Wed, Dec 12, 2012 at 01:59:55PM -0800, Dan Gohman wrote: > The bug here isn't in clang's use of noalias or in BasicAliasAnalysis' > implementation of noalias; it's in the code that's optimizing the > icmp. Let's come back to this. The attached patch decouples InstSimplify from the alias analysis and provides the conservative logic for when pointers are not

> On 2016-Feb-05, at 15:22, James Y Knight <jyknight at google.com> wrote: > > That usually happens when someone deletes and then recreates an svn branch with the same name, as happened in r215001 and r215011. > It can be deleted now, if anyone wants to. ``` $ git push llvm.org :release_35 at 215010 fatal: unable to access 'http://llvm.org/git/llvm.git/': The requested

On Sun, Jun 26, 2016 at 2:48 PM, Renato Golin <renato.golin at linaro.org> wrote: > On 26 June 2016 at 13:31, Anton Korobeynikov via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> What you're probably missing is that 3.8.1 is made in release_38 >> branch. So, everything is there and already mirrored. >> >> Source tarballs will be available upon the