similar to: [LLVMdev] newbie question regarding llvm-mingw

I just built LLVM 2.0 on Windows with Visual C++ 2005. After a few tweaks, it produced several nice .exe files. I tried to compile a simple Hello-World program as given in the documentation: -------------------------------------------------------------------------------------- ; Declare the string constant as a global constant... %.LC0 = internal constant [13 x i8 ] c"hello

Hello, Ralf > ERROR: Program used external function '__main' wich could not be > resolved! This was the bug fixed soon after 2.2 release. > I get the same error if I link the program with: "llvm-ld -v --stats > hello_world.bc -o hello_world.exe" > ... and execute the resulting "hello_world.exe" Right, because produced .exe just calls lli for bytecode

On Nov 7, 2007, at 6:10 PM, Antony Blakey wrote: > Hi, > I'm experimenting with using LLVM to generate dynamic FFI bridges > in VisualWorks Smalltalk. LLVM is an amazing thing! I'm going from > dynamically generated assembler source to machine code, and I have > that all working, copied from the llc tool and the JIT example. I > have two questions: > > 1. What

Hi, I'm experimenting with using LLVM to generate dynamic FFI bridges in VisualWorks Smalltalk. LLVM is an amazing thing! I'm going from dynamically generated assembler source to machine code, and I have that all working, copied from the llc tool and the JIT example. I have two questions: 1. What optimization passes, if any, should I run on the module before I pass it to the

I am forwarding a question and response about the use of getelementptr: > Hi. I found an LLVM code example that might be an error. The relevant > URL is: http://llvm.cs.uiuc.edu/docs/LangRef.html#modulestructure > > There is a piece of code which looks like this: > > ; Declare the string constant as a global constant... > %.LC0 = internal constant [13 x sbyte] c"hello

Hello again, I'm exploring llvm's intermediary representation with this code: //////////////////////////////////// %.LC0 = internal constant [13 x sbyte] c"hello world\0A\00" declare int %puts(sbyte*) implementation int %main() { %cast210 = getelementptr [13 x sbyte]* %.LC0, long 0, long 0; call int %puts(sbyte* %cast210) ret int 0 }

lli executed the bytecode corresponding to test_3.0_ml.ll without a failure, even though Function() is accessing an invalid memory address. The original code is in test_3.0.c, and the malloc() in Create() has been replaced by alloca() in test_3.0_ml.ll. I expected lli to segfault or similar when testing my code. Are my assumptions erroneous? -------------- next part --------------

Hi, ? Is there a fix for this issue??? ---> http://permalink.gmane.org/gmane.comp.audio.compression.speex.devel/2959 ? I am seeing the same thing when I compile speex in visualdsp ? These are the errors I get from using the assembly version of vq_nbest: ? ..\..\..\..\algorithms\voice\speex\src\vq.c [Error ea5004] "C:\Users\coder\AppData\Local\Temp\acc22e8547f000\acc22e8547f001.s":482

Can you add `--reproduce=repro` to lld command line? That generates repro.tar in your current directory which contains all input files. And then please compress and upload it somewhere so that we can take a look. On Mon, Apr 2, 2018 at 9:18 AM Andrew Kelley via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Alpine linux is a distribution that uses musl libc instead glibc. Here are

https://superjoe.s3.amazonaws.com/temp/repro.tar.xz On Mon, Apr 2, 2018 at 1:26 PM, Rui Ueyama <ruiu at google.com> wrote: > Can you add `--reproduce=repro` to lld command line? That generates > repro.tar in your current directory which contains all input files. And > then please compress and upload it somewhere so that we can take a look. > > > On Mon, Apr 2, 2018 at

Alpine linux is a distribution that uses musl libc instead glibc. Here are my steps to reproduce: On Alpine linux, download LLVM, Clang, LLD 6.0.0 from releases.llvm.org, and build them from source. $ clang -c hello_world.c $ ld.lld --gc-sections -m elf_x86_64 -o hello_world /usr/lib/gcc/x86_64-alpine-linux-musl/6.4.0/../../../../lib/Scrt1.o

Howdy! I am trying to understand how to properly use dragonegg. I've gotten it on my machine and it runs everything and seems to compile fortran well. If I run this command: gcc-4.6 tests/hello_world.f -o hello_world.o -fplugin=./dragonegg.so -S -flto I get a bunch of LLVM code in the hello_world.o file. What do I do with it next if I want to execute it? I've tried llvm-as and llvm-nm but

GCC LTO works ok for the test case with both bfd and gold linker. David On Tue, Oct 4, 2016 at 6:58 AM, Teresa Johnson <tejohnson at google.com> wrote: > > > On Mon, Oct 3, 2016 at 6:15 PM, Teresa Johnson <tejohnson at google.com> > wrote: > >> >> >> On Mon, Oct 3, 2016 at 5:24 PM, Xinliang David Li <xinliangli at gmail.com> >> wrote:

On Mon, Oct 3, 2016 at 5:24 PM, Xinliang David Li <xinliangli at gmail.com> wrote: > Small repro: > > __attribute__((weak)) int hello_world(); > > int test() { > if (hello_world) > return hello_world(); > return 0; > } > > $ clang -fuse-ld=gold -flto=thin -O2 -shared -fPIC -o libmore.so more.c > $ objdump -t libmore.so |grep hello >

Hi all, int main() { t(""); return 0; } On Mac OS X, llvm-gcc compiles the zero-sized string to: .lcomm LC,1,0 gcc: .cstring LC0: .ascii "\0" The difference seems innocent enough. However, in objc if the zero- sized string is part of a cfstring, it causes a problem. The linker expects it in the readonly __cstring section, but llvm puts it in the

On 07/30/2014 10:06 AM, Larry Evans wrote: > On 07/30/2014 12:35 AM, Ben Pope wrote: >> On Wednesday, July 30, 2014 01:31 PM, Ben Pope wrote: >> >>> ldd your_built_clang | grep libstdc++ >>> chrpath -l your_built_clang >> >> Hmm, where "your_built_clang" should be the actual failing executable: >>

Hello all, How does one enter multi-line content using ''puppet resource file ...'' at the command line? For example, I am trying to create a file called /tmp/hw.txt with two lines of content: $ cat /tmp/hw.txt hello world This does not work: $ puppet resource file hello_world \ path=/tmp/hw.txt \ ensure=file \ content="hello\nworld\n" This does, but use

Hello, With GCC, it is possible to compile GIMPLE from an object file back to assembly. With Dragonegg, it seems to be a NOP. (See below for a comparison.) This appears it could be a nice way to mix the strengths of GCC and LLVM. If it worked.. Should it? Thanks, Marcus [mdaniels at dn002 dragonegg]$ cat hello.c #include <stdio.h> int hello () { printf ("Hello

> > I volunteer. As soon as I get everything to work. > > > > Next problem: I now have the hello.bc file compiled. But how do I get an executable from this? I tried: > > > > C:\Eigenes\compiler\llvm-2.0\win32\release>llvm-ld -o=hellow.exe hellow.bc > > llvm-ld: Could not find llvm-stub.exe executable! > > > > So, I don't have

Trying to run this exec in one of our manifests. When the resource is run during a puppet run, it returns a error code 87. But when I execute the same command on command prompt, it returns 3010. Is there any way to dig and and find out why the return codes are different. FYI, I am using the sysnative path to avoid the file system redirection on windows. Platform: Windows 2008R2 64 bit