similar to: [LLVMdev] Re: C back-end for llvmg++

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

Hi: I'm interested in using llvm to convert C++ code to C code. I used the following command to do this: % llvm-g++ -c foo.cpp -o - | llc -march=c -o foo.cbe.c In the resulting file foo.cbe.c there are many occurences of '0x0p+0'. What is it used for? Here's a code snippet from the file foo.cbe.c if ((ltmp_126_2 > 0x0p+0)) { goto ltmp_363_19; } else { goto

After converting a piece of C++ code to C one of the functions that are generated is this: _ZStlsISt11char_traitsIcEERSt13basic_ostreamIcT_ES5_PKc Where is it defined and where can I find the source for it? I need the source to compile it with a C compiler (AMPC) that will convert the C code to Java Bytecode. If the above function is in C++ then I need to convert it to C first. Here's the

Hi: I've been able to compile the attached "helloworld.c" file converted from "helloworld.cpp". My question is how does one usually use __main() and CODE_FOR_MAIN() in tying up with the rest of the code? Attached here are the original "helloworld.cpp" and "helloworld.c" files. Thanks. Napi On Sun, 2006-11-05 at 09:14 -0800, Reid Spencer wrote: >

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

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 several years ago? >>> >> Hi Napi, >> >> For one, it converts

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++

On Thu, 2006-11-16 at 21:08 -0800, Chris Lattner wrote: > On Fri, 17 Nov 2006, Mohd-Hanafiah Abdullah wrote: > > After converting a piece of C++ code to C one of the functions that are > > generated is this: > > _ZStlsISt11char_traitsIcEERSt13basic_ostreamIcT_ES5_PKc > > This is defined in the C++ standard library. You can get the demangled > name like so: > $

I've read and followed the README.LLVM file that comes with LLVM-GCC 4.0 Front End source, but got the following error when compiling: configure: error: You must specify valid path to your LLVM tree with --enable-llvm=DIR make: *** [configure-gcc] Error 1 I've done the following in csh before hand: $ setenv LLVMOBJDIR /home/napi/proj/c2jvm/llvm/llvm-gcc/obj Where did I go wrong?

On Sat, 2006-11-04 at 21:06 -0800, Reid Spencer wrote: > Hi Napi, > > On Sun, 2006-11-05 at 12:40 +0800, Mohd-Hanafiah Abdullah wrote: > > Hi: > > > > I'm interested in using llvm to convert C++ code to C code. > > I used the following command to do this: > > > > % llvm-g++ -c foo.cpp -o - | llc -march=c -o foo.cbe.c > > Yup, that'll

How does the C back-end of LLVM differ from the one in gcc2c developed by SUN several years ago? Thanks. Napi

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 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; } > > $

Hi Napi, On Mon, 2006-11-06 at 10:44 +0800, Mohd-Hanafiah Abdullah wrote: > Hi: > > I've been able to compile the attached "helloworld.c" file converted > from "helloworld.cpp". Great. > > My question is how does one usually use __main() and CODE_FOR_MAIN() > in tying up with the rest of the code? I'm not quite sure what you're asking.

On Sun, 2006-11-05 at 19:06 -0800, Reid Spencer wrote: ... > As for the __main function, its a gcc library call required by the > compiler for program startup. The details vary but the call is needed. > Amongst other things it will probably initialize your C++ static > constructors. Hi Reid: I'm not using gcc for this purpose but another C compiler called AMPC. It compiles C

On Fri, 17 Nov 2006, Mohd-Hanafiah Abdullah wrote: > After converting a piece of C++ code to C one of the functions that are > generated is this: > _ZStlsISt11char_traitsIcEERSt13basic_ostreamIcT_ES5_PKc This is defined in the C++ standard library. You can get the demangled name like so: $ c++filt _ZStlsISt11char_traitsIcEERSt13basic_ostreamIcT_ES5_PKc std::basic_ostream<char,

Mohd-Hanafiah Abdullah wrote: > On Fri, 2006-11-17 at 11:43 -0800, Chris Lattner wrote: > >> On Fri, 17 Nov 2006, John Criswell wrote: >> >>> I don't think you will need to deal with any names. The C++ standard >>> library has already been compiled to LLVM bytecode (it is part of the >>> llvm-gcc/llvm-g++ distribution). If you use

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. As far as code quality, I don't believe it's been compared. -bw

On 11/05/07, Mohd-Hanafiah Abdullah <napi at axiomsol.com> wrote: > I've been looking for a C++ to C translator for quite some time. > The purpose is to support C++ for the compiler I developed targeting the > JVM. But the compiler I wrote only supports ANSI C (1989). So the C++ > to C translator is needed, and among the options are as follows: > [...] > c) LLVM

On Fri, 2007-05-11 at 23:15 -0400, me22 wrote: > On 11/05/07, Mohd-Hanafiah Abdullah <napi at axiomsol.com> wrote: > > I've been looking for a C++ to C translator for quite some time. > > The purpose is to support C++ for the compiler I developed targeting the > > JVM. But the compiler I wrote only supports ANSI C (1989). So the C++ > > to C translator is