Displaying 20 results from an estimated 4000 matches similar to: "[LLVMdev] clang looking for gold plugin when used with '-emit-llvm' option"
2012 May 17
2
[LLVMdev] clang looking for gold plugin when used with '-emit-llvm' option
Are you intending to try to link? That error message isn't coming from clang, but from /usr/bin/ld. If you just want the bitcode for the one source file, you need to pass "-c" as well, just like if you want an object file.
-Jim
On May 16, 2012, at 5:39 PM, Ashok Nalkund <ashoknn at qualcomm.com> wrote:
> Resending, can somebody please help?
>
> On 5/16/2012 2:47 PM,
2012 May 17
0
[LLVMdev] clang looking for gold plugin when used with '-emit-llvm' option
Resending, can somebody please help?
On 5/16/2012 2:47 PM, Ashok Nalkund wrote:
> Hi All,
> I built the binaries from the 3.1 final tag
> (http://llvm.org/svn/llvm-project/cfe/tags/RELEASE_31/final/ etc) as below:
>
>> ../llvm/configure --enable-targets=host-only --prefix=/local/mnt/workspace/ashoknn/crd/neo/llvmsvn/build/bin
>> make install
>
> I notice that
2012 May 17
0
[LLVMdev] clang looking for gold plugin when used with '-emit-llvm' option
MY BAD (in caps)...really sorry to have bothered. I was thinking of -S
-E options but forgot the -c option.
clang -c -emit-llvm test.c
lli test.o
both work fine :).
Thanks,
ashok
On 5/16/2012 5:45 PM, Jim Grosbach wrote:
> Are you intending to try to link? That error message isn't coming from clang, but from /usr/bin/ld. If you just want the bitcode for the one source file, you need to
2012 May 14
2
[LLVMdev] MCJIT
On May 14, 2012, at 11:12 AM, Ashok Nalkund <ashoknn at qualcomm.com> wrote:
> On 5/14/2012 10:40 AM, Ashok Nalkund wrote:
>>>
>>> Hm. OK, that's odd. It should change which constructor gets called in EngineBuilder::create() (which is in lib/ExecutionEngine/ExecutionEngine.cpp). Are you perhaps calling setUseMCJIT(true) after having already called create()? Can
2012 May 14
2
[LLVMdev] MCJIT
On 5/14/2012 9:18 AM, Jim Grosbach wrote:
>
> On May 14, 2012, at 9:07 AM, Ashok Nalkund<ashoknn at qualcomm.com> wrote:
>
>> I was able to get past the error by calling InitializeNativeTargetAsmParser() in my code. Now I have a failure in resolving external libraries, so looking into that (recompiled with --enable-ffi but I now get an error LLVMgold.so not found).
>>
2012 May 14
0
[LLVMdev] MCJIT
On 5/14/2012 10:40 AM, Ashok Nalkund wrote:
>>
>> Hm. OK, that's odd. It should change which constructor gets called in EngineBuilder::create() (which is in lib/ExecutionEngine/ExecutionEngine.cpp). Are you perhaps calling setUseMCJIT(true) after having already called create()? Can you step through EngineBuilder::create() and see what's happening there?
>>
>> -Jim
2012 May 13
1
[LLVMdev] Unable to link in X86AsmParser.cpp into lli
Hi,
Using the trunk of svn. I'm trying to get inline-asm working on X86.
So I added call to:
> InitializeNativeTargetAsmParser()
during initialization. However, this causes a linking error:
> llvm[2]: Linking Debug+Asserts executable lli
> /local/mnt/workspace/ashoknn/crd/neo/llvm/proto/llvmsvn/build/tools/lli/Debug+Asserts/lli.o: In function
2012 May 20
2
[LLVMdev] lli unable to resolve symbol _ZNKSt3__16locale9use_facetERNS0_2idE in bitcode
Hi,
LLVM/Clang version: 3.2svn (r156975). I have a bitcode file that I'm
trying to load/execute using lli as below but it reports an error about
unresolved symbol:
> LLVM ERROR: Program used external function '_ZNKSt3__16locale9use_facetERNS0_2idE' which could not be resolved!
> lli: /local/mnt/workspace/ashoknn/crd/neo/llvm/proto/llvmsvn/llvm/lib/Support/ThreadLocal.cpp:54:
2012 May 14
2
[LLVMdev] MCJIT
On 5/14/2012 10:28 AM, Jim Grosbach wrote:
>
> On May 14, 2012, at 10:21 AM, Ashok Nalkund<ashoknn at qualcomm.com> wrote:
>
>> On 5/14/2012 9:51 AM, Jim Grosbach wrote:
>>>
>>>>>
>>>>> If you're hitting that code, you're running the old JIT (which does indeed not support inline assembly), not the MCJIT.
>>>>>
2012 May 21
0
[LLVMdev] lli unable to resolve symbol _ZNKSt3__16locale9use_facetERNS0_2idE in bitcode
Resending, any pointers? I demangled the symbol and it turns out to be:
std::__1::locale::use_facet(std::__1::locale::id&) const
tia,
ashok
On 5/19/2012 9:41 PM, Ashok Nalkund wrote:
> Hi,
> LLVM/Clang version: 3.2svn (r156975). I have a bitcode file that I'm
> trying to load/execute using lli as below but it reports an error about
> unresolved symbol:
>> LLVM
2012 May 14
0
[LLVMdev] MCJIT
On May 14, 2012, at 9:42 AM, Ashok Nalkund <ashoknn at qualcomm.com> wrote:
>
> On 5/14/2012 9:18 AM, Jim Grosbach wrote:
>>
>> On May 14, 2012, at 9:07 AM, Ashok Nalkund<ashoknn at qualcomm.com> wrote:
>>
>>> I was able to get past the error by calling InitializeNativeTargetAsmParser() in my code. Now I have a failure in resolving external
2012 May 14
2
[LLVMdev] MCJIT
On 5/14/2012 9:51 AM, Jim Grosbach wrote:
>
>>>
>>> If you're hitting that code, you're running the old JIT (which does indeed not support inline assembly), not the MCJIT.
>>>
>>
>> Do I need to enable anything at configure, my configure looks like this:
>>> ../llvm/configure --enable-libffi --enable-targets=host-only
2012 May 14
0
[LLVMdev] MCJIT
On May 14, 2012, at 10:21 AM, Ashok Nalkund <ashoknn at qualcomm.com> wrote:
> On 5/14/2012 9:51 AM, Jim Grosbach wrote:
>>
>>>>
>>>> If you're hitting that code, you're running the old JIT (which does indeed not support inline assembly), not the MCJIT.
>>>>
>>>
>>> Do I need to enable anything at configure, my
2012 May 14
0
[LLVMdev] MCJIT
On May 14, 2012, at 9:07 AM, Ashok Nalkund <ashoknn at qualcomm.com> wrote:
> I was able to get past the error by calling InitializeNativeTargetAsmParser() in my code. Now I have a failure in resolving external libraries, so looking into that (recompiled with --enable-ffi but I now get an error LLVMgold.so not found).
>
> Then I hda to disable the following code in
2012 May 14
2
[LLVMdev] MCJIT
I was able to get past the error by calling
InitializeNativeTargetAsmParser() in my code. Now I have a failure in
resolving external libraries, so looking into that (recompiled with
--enable-ffi but I now get an error LLVMgold.so not found).
Then I hda to disable the following code in
lib/Target/X86/X86CodeEmitter.cpp:
> case TargetOpcode::INLINEASM:
> // We allow inline
2012 May 21
2
[LLVMdev] lli unable to resolve symbol _ZNKSt3__16locale9use_facetERNS0_2idE in bitcode
Ashok Nalkund wrote:
> Resending, any pointers? I demangled the symbol and it turns out to be:
> std::__1::locale::use_facet(std::__1::locale::id&) const
My guess is that you've got a .bc file produced on a mac using libc++
(hence the ::_1 part) and you're trying to run it on linux with
libstdc++ (which doesn't use inline namespaces, the '::_1::' part). That
2012 Jun 19
2
[LLVMdev] Is cross-compiling for ARM on x86 with llvm/Clang possible?
Hello Gergö, Joerg and people on our list
With your kind answer, I tried to build a hello world program for
ARM(arm-none-linux-gnueabi) on my x86-64 PC.
Thank you we verified the generated bitcode. The only thing remained is
linking.
Let me brief what I did so far.
1. Built Clang/llvm in a way explained in
http://clang.llvm.org/get_started.html on Ubuntu 11.10 x86-64 PC
2. Downloaded gcc-4.0
2012 Jun 19
0
[LLVMdev] Is cross-compiling for ARM on x86 with llvm/Clang possible?
Hello
> ./clang -v -emit-llvm -ccc-host-triple arm-none-linux-gnueabi
> -I/home/hum/Documents/Projects/llvm_clang/gnuarm-4.0.2/arm-elf/include
> -L/home/hum/Documents/Projects/llvm_clang/gnuarm-4.0.2/arm-elf/bin hello.c
You forgot about sysroot here.
> /home/hum/Documents/Projects/llvm_clang/gnuarm-4.0.2/arm-elf/bin/ld:
> unrecognised emulation mode: armelf_linux_eabi
>
2012 Jun 18
0
[LLVMdev] Is cross-compiling for ARM on x86 with llvm/Clang possible?
On Sat, Jun 16, 2012 at 08:20:23PM +0900, Journeyer J. Joh wrote:
> If the cross compiling is supported, is there any documentation on how to
> do it?
The short version is: assuming you have a cross-binutils installation
using e.g. x86_64--netbsd-as and x86_64--netbsd-ld, you add a symlink
called x86_64--netbsd-clang to clang and just call that with an
appropiate --sysroot to make it find
2019 Sep 30
3
Debugging LowerTypeTests in LLVM Using GDB
Hi,
I am looking into Control-Flow Integrity for indirect function calls,
implemented with jump tables. I want to step through the code that produces
these jump tables in GDB. I have built clang and opt from source with
debugging symbols. I believe this code lives in
llvm/lib/Transforms/LowerTypeTests.cpp, but when I try to debug *opt* by
running the command "run -lowertypetests cfi-icall.bc