similar to: [LLVMdev] Difficulty compiling LLVM-based tools with clang

On 11-05-12 8:33 PM, Talin wrote: > I recently modified my compiler's build files to use clang if it detects > its available, however I'm running into a number of problems with this. > I'm having one set of problems on OS X, and a different set of problems > under Ubuntu. > > In both cases I'm attempting to link my frontend - compiled with clang - > against the

On 5/12/11 7:08 PM, Rafael Ávila de Espíndola wrote: > The problem comes from SearchForAddressOfSpecialSymbol.cpp: > > // FIXME: Currently disabled when using Clang, as we don't always > have our > // runtime support libraries available. > #ifndef __clang__ > #ifdef __i386__ > EXPLICIT_SYMBOL(__eprintf); > #endif > #endif > > Now, exactly

I have a problem where my LLVM-generated code works on Linux but not on OS X, and the problem involves non_lazy_ptr. I have an external symbol named "@gc_safepoint_map", which is generated by the linker's GCStrategy plugin. Since it is not generated until link time, I declared it as an external symbol so that the modules that use it can compile without error. Here's what the

So, I've got a case where I am attempting to pass the address of a static symbol from a module written in Tart (the language I am working on), to a module written in C (which is part of Tart's runtime library). This works fine on Linux, but fails on OS X because the address being passed is the "non_lazy_ptr" symbol, not the symbol itself. In my .bc file, I've got code that

On May 18, 2008, at 11:51 PM, Talin wrote: > Anton Korobeynikov wrote: >> Hello Talin, >> >>> Yes exactly. I'm on OS X (x86), and I'm not specifying a target - I >>> assumed that it would choose sensible defaults... >>> >> Could you please provide a .bc testcase? There can be multiple >> issues, >> but at the first glance it

Here's a more specific question about compiling native code: When I use llc to generate a .s file, and then I try to assemble it using 'as', I get tons of errors - it appears to be choking on lines like the following: movl L"_tart.core.Iterable<tart.core.String>:type"$non_lazy_ptr, %eax The error I get is:

Hi All, I'm working on various cleanups and simplifications to the asmprinters. One thing that is driving me nuts is that the asmprinters currently "reverse engineer" a lot of information when printing an operand that isel had when it created it. I'm specifically talking about all the suffixes generated by isel, like $non_lazy_ptr, @TLSGD, @NTPOFF, (%rip) etc. These

Please don't be alarmed by the failed compiles on llvm-ppc-darwin. They are likely not your fault. I'm trying to get a PPC build bot setup (arxan_bellini), and so far it's dying here: Linking CXX shared library ../../lib/libgtest.dylib Undefined symbols: "vtable for llvm::raw_ostream", referenced from: __ZTVN4llvm11raw_ostreamE$non_lazy_ptr in gtest.cc.o

Hi there, Inspired by the recent FOSDEM keynote, I've tried to write an LLVM backend for the STM8 microcontroller platform. The STM8S-Discovery evaluation board [1] has been handed out for free or is sold dirt- cheap, but there is no Open Source cross-compiler for it. The available ST assembler, linker and USB flash programmer are closed- source Windows binaries. And the compiler

I'm trying to compile LLVM with musl libc library. The compilation process fails on the following: x86_64-linux-musl-g++ -DGTEST_HAS_RTTI=0 -DLLVM_BUILD_GLOBAL_ISEL -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -Ilib/Support -I../lib/Support -Iinclude -I../include -fPIC -fvisibility-inlines-hidden -Werror=date-time -std=c++11 -Wall -W -Wno-unused-parameter

On Sun, Feb 20, 2011 at 4:23 PM, Andreas Färber <andreas.faerber at web.de> wrote: > Hi there, > > Inspired by the recent FOSDEM keynote, I've tried to write an LLVM > backend for the STM8 microcontroller platform. The STM8S-Discovery > evaluation board [1] has been handed out for free or is sold dirt- > cheap, but there is no Open Source cross-compiler for it. The >

Hello, Bill. > It's not exactly tweaking magic knobs. It's doing something that's > already done -- putting the information in the TAI object, and > allowing the specific back-end to set the appropriate strings. It seems to me, that simple strings / bools there are not enough :) "$non_lazy_ptr" emission is already in asm printers (in 2 places!). The

Hi, I tried to implement an 'llc'-like tool in my project to manage different passes and a target machine. I use given llvm project structure to avoid problems but I have a link problem and don't know how to solve it: The target machine uses 'FindUsedTypes' pass and when I try to use my target machine in the tool I got "Undefined symbols:

> And be warned that the PC doesn't point at the next instruction when you use it like this - I believe you don't need to modify it at all if you swap the pop and the .long. Bernie, is it related to ARM pipeline? I'm interesting in this, is there any other additional information? On Fri, Mar 8, 2013 at 4:59 AM, Tim Northover <t.p.northover at gmail.com>wrote: > Hi Ashi,

Hi Anton, >> It's not exactly tweaking magic knobs. It's doing something that's >> already done -- putting the information in the TAI object, and >> allowing the specific back-end to set the appropriate strings. > It seems to me, that simple strings / bools there are not enough :) > "$non_lazy_ptr" emission is already in asm printers (in 2 places!).

Hello Talin, > Yes exactly. I'm on OS X (x86), and I'm not specifying a target - I > assumed that it would choose sensible defaults... Could you please provide a .bc testcase? There can be multiple issues, but at the first glance it seems, that names were not properly mangled. -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg

Anton Korobeynikov wrote: > Hello Talin, > >> Yes exactly. I'm on OS X (x86), and I'm not specifying a target - I >> assumed that it would choose sensible defaults... >> > Could you please provide a .bc testcase? There can be multiple issues, > but at the first glance it seems, that names were not properly mangled. > I've created bug

Dear Nico, I believe you need to add LLVMipa to the list of libraries to link into your tool. FindUsedTypes::ID is defined in lib/Analysis/IPA. I think it would be LLVMipa.a if you added it to LLVMLIBS and ipa if you added it to LINK_COMPONENTS. -- John T. Nico wrote: > Hi, > > I tried to implement an 'llc'-like tool in my project to manage > different passes and a

On Tue, 4 May 2004, Chris Lattner wrote: > On Tue, 4 May 2004, Chris Lattner wrote: > > I suspect that a large reason that LLVM does worst than a native C > > compiler with the CBE+GCC is that LLVM generates very low-level C code, > > and I'm not convinced that GCC is doing a very good job (ie, without > > syntactic loops). > > Yup, this is EXACTLY what is

Hi Folks, I am building LLVM 3.9.1 using the Yocto build system for a cross build. The compiled bins/libs work totally fine on the target machine however there seems to be an intermittent race condition during the build which causes a build failure. On the failed builds I usually see things being linking/compiling twice e.g. Linking CXX static library ../libLLVMSupport.a cd