search for: liquido2

"Michael Ness" <mike at liquido2.com> writes: > Some additional information about the setup may be of interest: > > I'm using CMake to generate the make files for MSYS. All appears to go well > until the tools are compiled. > > The undefined references seem to be coming from the libraries that were just...

...------------------------------------------------ From: "Óscar Fuentes" <ofv at wanadoo.es> Sent: Tuesday, December 08, 2009 1:31 PM To: <llvmdev at cs.uiuc.edu> Subject: Re: [LLVMdev] Rebuilding LLVM libraries with LLVM-GCC on Windows > "Michael Ness" <mike at liquido2.com> writes: > >> Some additional information about the setup may be of interest: >> >> I'm using CMake to generate the make files for MSYS. All appears to go >> well >> until the tools are compiled. >> >> The undefined references seem to be com...

"Michael Ness" <mike at liquido2.com> writes: [snip] > I then used both of these builds to attempt to assemble and link my > project with llvm-g++: > > $ llvm-g++ out.s -o out.exe `llvm-config --ldflags --libs x86 core > system support` > > gave me the errors found in the attached file "errors_gcc.tx...

"Michael Ness" <mike at liquido2.com> writes: > I decided to forget 2.5 and move on to 2.6 which built fine with CMake. > However, I continue to have problems with llvm-config when using the > following command: > > $ llvm-g++ out.s -o out `llvm-config --ldflags --libs core support system > x86` > >...

I'm attempting to use file I/O across platforms from LLVM assembly using the standard GNU C library: fprintf(), stdin/stdout, etc. Ideally I'd like to simply provide a single bitcode file that could be compiled on each platform, but because the internals of the I/O on each platform is different, this is not currently workable. So my question is this: How do you suggest doing I/O in a

"Michael Ness" <mike at liquido2.com> writes: > I'm attempting to use file I/O across platforms from LLVM assembly > using the standard GNU C library: fprintf(), stdin/stdout, etc. > Ideally I'd like to simply provide a single bitcode file that could be > compiled on each platform, but because the internals...

Some additional information about the setup may be of interest: I'm using CMake to generate the make files for MSYS. All appears to go well until the tools are compiled. The undefined references seem to be coming from the libraries that were just compiled: ../../lib/libLLVMBitReader.a(BitcodeReader.cpp.obj):fake:(.rdata$linkonce_ZTVN4llvm8ConstantE+0x10): undefined reference to

-------------------------------------------------- From: "Óscar Fuentes" <ofv at wanadoo.es> Sent: Friday, December 11, 2009 4:32 PM To: <llvmdev at cs.uiuc.edu> Subject: Re: [LLVMdev] Rebuilding LLVM libraries with LLVM-GCC on Windows > > You are working with an assembler file. Why? Here is the build process I'm using for my project: I have a program written in

Ok, more recent developments follow. I updated my MSYS and MinGW install to use binutils 2.20 and gcc 4.4.0. With this I was able to build LLVM 2.6 with the following CMake configuration: cmake -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_PIC=NO -DLLVM_ENABLE_THREADS=NO -G "MSYS Makefiles" ~/llvm-2.6-src I also downloaded the llvm-gcc 4.2 binaries from llvm.org and used them to

Hello again, In order to avoid the set jump/long jump dependency of DLLs built under Visual C++, we're trying to build the libraries and tools under LLVM-GCC so it will use DWARF exception handling instead of SJ/LJ. The problem we're running into is that the libraries that we just finished creating cannot be found later in the build process when OPT tries to build. My partner has MinGW

Thanks everyone, a set of wrapper routines it will be then. Dustin, are the routines you wrote open source or do you know if there is already a project that provides such a portable interface to libc for LLVM? If not, I'll write my own routines, but if there is a way to adopt a common standard or avoid reinventing the wheel I'm all for it. Mike

I'm attempting to modify a parser generator to emit LLVM code instead of C. So far the experience has been trivial, but I am now running into an error regarding labels that I can't seem to solve. Situation 1: A label is used immediately after a void function call (l6 in this case): <snip> %tmp26 = load i32* @yybegin, align 4 %tmp27 = load i32* @yyend, align 4 call void