Displaying 20 results from an estimated 20000 matches similar to: "[LLVMdev] generating executable file from .ll files"
2013 Jan 12
0
[LLVMdev] generating executable file from .ll files
Hi Ali,
> I'm writing a front-end for llvm with java. my front-end produces .ll files.
> Then I use the following commands to convert these files to an executable file:
> !. for each .ll file I use 'llvm-as file.ll' to create a bitcode file
> 2. use 'llvm-ld -o executable my-bitcode-files -L/usr/lib/i386-linux-gnu
> -lstdc++' to generate an executable file
2013 Jan 09
0
[LLVMdev] linking llvm libraries with bitcode files
On Wed, Jan 9, 2013 at 5:32 AM, Ali Sedaghat <ali.sedaghatbaf at gmail.com> wrote:
> I'm developing an llvm-based compiler and when I try to generate
> executable file the following error occurs:
>
> ./bin/llvmcode.s:35: undefined reference to `operator new[](unsigned
> long)'
>
> Note that in the generated IR, the function '@_Znam' is called which is
2013 Jan 09
2
[LLVMdev] linking llvm libraries with bitcode files
I'm developing an llvm-based compiler and when I try to generate
executable file the following error occurs:
./bin/llvmcode.s:35: undefined reference to `operator new[](unsigned
long)'
Note that in the generated IR, the function '@_Znam' is called which is
located in one of llvm libraries. So, I should have linked the generated
assembly file with that library. Here is the code I
2012 Jan 24
2
[LLVMdev] Convert .ll file to .c file
Hi,
I wanted to convert .ll file to .c file (for the sake of debugging the
c file). I used the command "llc" with "-march=c" option. But i'm getting
the below error.
*llc: error: invalid target 'c'*
*
*
My script file code for converting it is:
llvm-as -f module.ll
opt -o=module.bc module.bc
llvm-dis module.bc
llc -f -march=c module.bc
#gcc
2019 Jan 02
2
[HWASAN] Is Buildbot missing hwasan tests?
After updating from trunk today, I am seeing this failure in hwasan:
FAIL: HWAddressSanitizer-x86_64 :: TestCases/sizes.cpp (19011 of 49508)
******************** TEST 'HWAddressSanitizer-x86_64 :: TestCases/sizes.cpp' FAILED ********************
<snip>
Command Output (stderr):
--
+ : 'RUN: at line 1'
+ /build/./bin/clang --driver-mode=g++ -fsanitize=hwaddress -mllvm
2019 Jan 02
3
[HWASAN] Is Buildbot missing hwasan tests?
This commit has added __hwasan_memset to compiler-rt:
commit 749bd83b08b7239f5d18c4e3095183919c68eb30
Author: Eugene Leviant <eleviant at accesssoftek.com>
Date: Thu Dec 20 09:10:03 2018 +0000
[HWASAN] Add support for memory intrinsics
This is patch complements D55117 implementing __hwasan_mem*
functions in runtime
Differential revision: https://reviews.llvm.org/D55554
2012 Jan 24
0
[LLVMdev] Convert .ll file to .c file
Sarath Chandra wrote:
> Hi,
>
> I wanted to convert .ll file to .c file (for the sake of debugging
> the c file). I used the command "llc" with "-march=c" option. But i'm
> getting the below error.
>
> * llc: error: invalid target 'c' *
> *
> *
> My script file code for converting it is:
>
> llvm-as -f module.ll
> opt
2010 Aug 05
2
[LLVMdev] [PATCH] Capability of Win32.DLL with ENABLE_SHARED
Good summer, all!
This patch enables ENABLE_SHARED=1 to build DLL based LLVM toolchain.
I have checked this on Cygwin-1.5, Cygwin-1.7, mingw(msysgit) and
mingw-cross-fedora12.
I can separate this patch into some parts; cleanups, adding
definitions and adding rules.
Any feedbacks are welcome.
Have fun!
...Takumi
* Pros
- reduction of linking time of toolchain.
- capability of -load
2012 Jan 24
1
[LLVMdev] Convert .ll file to .c file
Hi Nick,
I need the module.ll file. Now how can i configure LLVM to enable "c"
target? Is it that i need to build from the scratch? Is there any way to
enable 'c' target also?
On Tue, Jan 24, 2012 at 12:10 PM, Nick Lewycky <nicholas at mxc.ca> wrote:
> Sarath Chandra wrote:
>
>> Hi,
>>
>> I wanted to convert .ll file to .c file (for the
2013 Oct 12
1
[LLVMdev] Fwd: unsupported gc: vmkit
when I execute clang on llvm bitcode files, I get the following error:
clang: error: unable to execute command: Aborted
unsupported GC: vmkit
UNREACHABLE executed at GCMetadata.cpp:87!
0 clang 0x09e9d5d9 llvm::sys::PrintStackTrace(_IO_FILE*) + 41
Stack dump:
0. Program arguments: /home/ali/llvm-3.3.src/Release+Asserts/bin/clang
-cc1 -triple i386-pc-linux-gnu -emit-obj -mrelax-all
2013 Jan 14
2
[LLVMdev] linking standard c++ functions @_Znam and @_Znwm
I'm new to c++ programming and currently working on an llvm front-end
development project. When I link the object files created by llc, my linker
cannot locate the following functions. I know that these are standard c++
library functions but g++ cannot locate them. Now my question is that where
are these functions defined and how can I link them with my object files,
and actually what do they
2008 Feb 27
1
[LLVMdev] llvm-ld behavior change?
Before:
/Users/echeng/LLVM/llvm/Release/bin/llvm-ld -L/Developer/usr/llvm-
gcc-4.2/lib/gcc/i686-apple-darwin9.2.0/4.2.1 -L/Developer/usr/llvm-
gcc-4.2/lib Output/444.namd.linked.bc -lc -lstdc++ -lm -o Output/
444.namd.llvm
llvm-ld: warning: Cannot find library 'stdc++'
Now:
/Users/echeng/LLVM/llvm/Release/bin/llvm-ld -L/Developer/usr/llvm-
2004 Sep 10
2
Re: non-PIC code in shared libs again
On Tue, Feb 11, 2003 at 05:14:45PM +0000, Christian Weisgerber wrote:
> Ben Hines <bhines@alumni.ucsd.edu> wrote:
>
> > The patch fixed the problem with your libs. However, when linking the
> > xmms plugin i still get:
> >
> > *** Warning: This library needs some functionality provided by -lstdc++.
>
> This is because of id3lib, which is written in
2012 Jun 08
4
Multiple sub-architecture: linking issue
Hi again,
following my previous post on RCurl, I cannot install Rcpp either:
g++ -m32 -I/home/renaud/bin/R/2.15/lib64/R/include
-I/home/renaud/bin/R/2.15/lib64/R/include/i386 -DNDEBUG
-I../inst/include/ -I/usr/local/include -fpic -g -O2 -c r_cast.cpp
-o r_cast.o
g++ -m32 -shared -L/usr/local/lib64 -o Rcpp.so Date.o DateVector.o
Datetime.o DatetimeVector.o Dimension.o DottedPair.o
2012 Jun 08
4
Multiple sub-architecture: linking issue
Hi again,
following my previous post on RCurl, I cannot install Rcpp either:
g++ -m32 -I/home/renaud/bin/R/2.15/lib64/R/include
-I/home/renaud/bin/R/2.15/lib64/R/include/i386 -DNDEBUG
-I../inst/include/ -I/usr/local/include -fpic -g -O2 -c r_cast.cpp
-o r_cast.o
g++ -m32 -shared -L/usr/local/lib64 -o Rcpp.so Date.o DateVector.o
Datetime.o DatetimeVector.o Dimension.o DottedPair.o
2013 Aug 23
1
[LLVMdev] gsplit-dwarf broken on Linux?
Hi!
Quick question - do you know if recent commits could cause this error, or I
should go to bisect/debug this? Do we have tests that check that
-gsplit-dwarf succeeds (i.e. compile and link step work)?
$ cat a.cc
int foo(int x) {
return x + 1;
}
int main() {
return foo(42);
}
$ ./bin/clang++ -gsplit-dwarf a.cc
/tmp/a-005b1a.o(.debug_pubnames+0x6): error: undefined reference to
2004 Sep 10
4
non-PIC code in shared libs again
On Wednesday, February 5, 2003, at 10:47 PM, Josh Coalson wrote:
> --- Matt Zimmerman <mdz@debian.org> wrote:
>
> good, very good. it may take me a little bit to get to it
> since I'm starting a new job next week.
>
> Ben, can you inspect the patch and confirm that it covers
> what you also suggested?
The patch fixed the problem with your libs. However, when
2010 Jan 05
1
[LLVMdev] [PATCH] test-suite/bullet: unbreak linking
Eliminate undefined references to powf, sqrtf and friends.
Index: MultiSource/Benchmarks/Bullet/Makefile
===================================================================
--- MultiSource/Benchmarks/Bullet/Makefile (revision 92512)
+++ MultiSource/Benchmarks/Bullet/Makefile (working copy)
@@ -1,7 +1,7 @@
LEVEL = ../../../
PROG = bullet
CPPFLAGS += -I$(PROJ_SRC_DIR)/include -DNO_TIME
-LDFLAGS
2016 Jul 23
3
[llvm-toolchain v3.8.1] LTO: Linking clang hangs with ld.gold and LLVMgold.so plugin
> On Jul 23, 2016, at 1:53 PM, Sedat Dilek via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote:
>
> On Sat, Jul 23, 2016 at 7:48 PM, Piotr Padlewski <prazek at google.com <mailto:prazek at google.com>> wrote:
>> How big is your project?
>> LTO eats RAM even faster than chrome. For example linking clang with LTO
>>
2019 Jan 04
2
[Fuzzer] Test failure on Linux x86-64
Continuing my quixotic effort to get 'check-all' clean, I am seeing a
Fuzzer failure on x86-64 Linux. Do any builders run fuzzer tests?
FAIL: libFuzzer :: value-profile-mem.test (103 of 103)
******************** TEST 'libFuzzer :: value-profile-mem.test' FAILED ********************
Script:
--
: 'RUN: at line 4'; /build/x86_64/./bin/clang --driver-mode=g++ -std=c++11