similar to: [LLVMdev] libstdc++ as bytecode, and compiling C++ to C

On Tue, Nov 21, 2006 at 05:33:32PM +0800, Mohd-Hanafiah Abdullah wrote: > Emil: > > I'm using LLVM 1.9 now. When I tried to do what you did I got the > following though: > > $ llvm-g++ -emit-llvm -c x.cpp > $ llvm-link -o=linked.o x.o std/*.o sup/*.o > WARNING: Linking two modules of different target triples! > WARNING: Linking two modules of different target

On Tue, 21 Nov 2006, Emil Mikulic wrote: > LLVMers, given the same endianness and pointersize, can one mix and > match LLVM bytecode files produced on different platforms? No, not in general. For example, on the mac, printf it often #defined to printf$ldbl, which doesn't exist on linux. System headers generally foil the ability to move stuff around like that. -Chris --

Anton Korobeynikov schrieb: > Hello, Philipp. > >> unsigned is 16 bit on my target platform. > Could you please show LLVM bytecode? > I've attached the .bc file and the .c source and output files. I compiled dusing llvm-gcc (not configured as cross-compiler though, so that might be the problem). Nevertheless I don't really see why portable source shouldn't be

Chris Lattner wrote: > On Tue, 21 Nov 2006, Emil Mikulic wrote: >> LLVMers, given the same endianness and pointersize, can one mix and >> match LLVM bytecode files produced on different platforms? > > No, not in general. For example, on the mac, printf it often #defined to > printf$ldbl, which doesn't exist on linux. System headers generally foil > the ability

[wincent at PC-BSD]export MAKE=gmake [wincent at PC-BSD]sudo R ..... > install.packages("Matrix") --- Please select a CRAN mirror for use in this session --- Loading Tcl/Tk interface ... done trying URL 'http://bibs.snu.ac.kr/R/src/contrib/Matrix_0.999375-9.tar.gz' Content type 'application/x-gzip' length 1483674 bytes (1.4 Mb) opened URL

Need to know if anyone has compiled the libstdc++ to LLVM bitcode. If it's available please where could I download it from? Thanks. Napi

On Fri, Sep 28, 2007 at 10:08:31AM +0800, Mohd-Hanafiah Abdullah wrote: > Need to know if anyone has compiled the libstdc++ to LLVM bitcode. If > it's available please where could I download it from? I did this last year. Check out: http://goanna.cs.rmit.edu.au/~emil/dietstdcxx.1.tar.bz2 --Emil

On Mon, 2006-11-20 at 17:49 +1100, Emil Mikulic wrote: > I've compiled all the object files that make up libstdc++ and libsupc++ > into LLVM bytecode: > http://goanna.cs.rmit.edu.au/~emil/libstdcxx.tar.bz2 (438KB) > > A simple test program, x.cpp: > > #include <iostream> > int main() { std::cout << "hello world\n"; return 0; } > > $

Emil: I'm using LLVM 1.9 now. When I tried to do what you did I got the following though: $ llvm-g++ -emit-llvm -c x.cpp $ llvm-link -o=linked.o x.o std/*.o sup/*.o WARNING: Linking two modules of different target triples! WARNING: Linking two modules of different target triples! WARNING: Linking two modules of different target triples! ... $ lli linked.o lli((anonymous

Hello Philipp, > Does that mean that I will have to configure llvm as a cross-compiler > even when using the C backend? Not llvm, but llvm-gcc only. I've successfully used llvm-gcc for crosscompiling with host=linux and target=mingw32 platform. So, you have just to supply host, build and target triples to llvm-gcc configure and be also sure, that configure will find target headers,

I've got this little program I wrote to test something, and it keeps giving the wrong result. I'm not inexperienced in C, but I can't believe strtof (et al) are broken, so I must be doing something wrong. However, I've spent hours looking at this and comparing it to the man pages and don't see what I'm doing wrong. strtod() and strtold() also give equally wrong results.

I am using R-2.6.0 on FreeBSD 8.0-CURRENT (i386). In the last days I had problems when building packages SparseM, lme4 and randomForest. The below message shows for randomForest, that 'libgfortran' was not found. The same error appeared with SparseM and lme4. --------------------------------- R CMD INSTALL randomForest_4.5-19.tar.gz * Installing to library

I've compiled all the object files that make up libstdc++ and libsupc++ into LLVM bytecode: http://goanna.cs.rmit.edu.au/~emil/libstdcxx.tar.bz2 (438KB) A simple test program, x.cpp: #include <iostream> int main() { std::cout << "hello world\n"; return 0; } $ llvm-g++ -emit-llvm -c x.cpp $ llvmc -o=out x.o std/*.o sup/*.o $ lli out.bc Segmentation fault (core

Hi, I have some questions about LLVM Since it is available in several and different platforms like Intel x86, PowerPc and Sparc, how do you handle the differences between these platforms in your bytecode? For example, Can a bytecode generated under MacOS run in the LLVM version under Linux x86? How do you handle things like little endian / big endian? How do you handle the difference in

Thx again Evan for the review. Here's a new patch for the JIT in itself. The major changes are: 1) A JITMemoryManager now has a flag saying "I require to know the size of what you want to emit" 2) DwarfJITEmitter is augmented with GetSize* functions 3) JITEmitter::startFunction checks if the JITMemoryManager requires to know the size. If so, it computes it and gives it through the

On Tue, 2007-05-08 at 11:58 -0700, Bill wrote: > On 5/8/07, Mohd-Hanafiah Abdullah <napi at axiomsol.com> wrote: > > How does the C back-end of LLVM differ from the one in gcc2c developed > > by SUN several years ago? > > > Hi Napi, > > For one, it converts LLVM's bytecode to C instead of GCC's RTL. It's > also under a different license. Hi

On Fri, 11 May 2007, me22 wrote: > I'm not exactly sure how llvm-g++ works. I think it goes through the > standard gcc sequence (gimple, rtl, and such) but then outputs LLVM > (http://llvm.org/docs/LangRef.html), which is the intermediate > representation used by the rest of the chain. To make an LLVM backend > you would not need to deal with RTL and such at all. llvm-g++

Dear all, Here's a new patch with Evan's comments (thx Evan!) and some cleanups. Now the (duplicated) exception handling code is in a new file: lib/ExecutionEngine/JIT/JITDwarfEmitter. This patch should work on linux/x86 and linux/ppc (tested). Nicolas -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: jit-exceptions.patch URL:

On Tue, 2007-05-08 at 22:45 -0700, Bill Wendling wrote: > On May 8, 2007, at 10:05 PM, Mohd-Hanafiah Abdullah wrote: > > > On Tue, 2007-05-08 at 11:58 -0700, Bill wrote: > >> On 5/8/07, Mohd-Hanafiah Abdullah <napi at axiomsol.com> wrote: > >>> How does the C back-end of LLVM differ from the one in gcc2c > >>> developed > >>> by SUN

Chris Lattner wrote: > Many aspects of the target compiler can leak through. So if one wants to use the LLVM system as a cross compiler, one has to configure llvm-gcc as a cross compiler? Fair enough, I guess. > One trivial example is: > > int X = sizeof(long); So I assume this also means that while getelementptr insulates llvm byte code from the details of target specific address