similar to: Expecting your phone call

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

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.

Mohd-Hanafiah Abdullah wrote: > 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

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: > $

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 Nov 19, 2004, at 9:25 PM, Mohd-Hanafiah Abdullah wrote: > Dear Dr Vikram: > > I need to know how to invoke llvmg++ so that it generates C code. Here's how you can do a single file (i.e., an unlinked executable): llvmg++ -c infile.cpp -o - | llc -march=c -o infile.cbe.c Reid might be able to tell you how to do it with a single command using the llvmc tool. In future, please

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

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 10/2/07, Mohd-Hanafiah Abdullah <napi at axiomsol.com> wrote: > 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

On Tue, 2007-10-02 at 11:47 -0700, Bill Wendling wrote: > On 10/2/07, Mohd-Hanafiah Abdullah <napi at axiomsol.com> wrote: > > 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 > >

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 a method/function from the standard C++ library. You can link it in at the bytecode level with: llvm-g++ -o output.bc <yourfile.bc> -lstdc++ You might also be able to do: llvm-g++

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

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 do it. Although you might want to do a little optimization otherwise you're going to get a lot of C code on

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?

Hi Napi, On Mon, 2006-11-06 at 12:17 +0800, Mohd-Hanafiah Abdullah wrote: > 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 > >