Anton Korobeynikov
2006-Nov-24 19:58 UTC
[LLVMdev] Byte code portability (was Re: libstdc++ as bytecode, and compiling C++ to C)
Hello Philipp.> Why does it need target libraries and binutils?gcc building process (and llvm-gcc4 as well) includes building of target-specific stuff including: 1. Building crt-support code on several platforms 2. Building libgcc.a[.so] 3. Building libstdc++.a[.so] If you don't want them to be built you should, probably you should consult gcc documentation to find right options or change build scripts.> Can't I just Compile my C++ code to C code (maybe using a template-only > libstdc++, so I won't have to link it) and then compile the resulting C > code with sdcc and link it to C libraries compiled directly with sdcc.Surely you can as soon as you have working llvm-gcc4. -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State University.
Philipp Klaus Krause
2006-Nov-24 20:30 UTC
[LLVMdev] Byte code portability (was Re: libstdc++ as bytecode, and compiling C++ to C)
Anton Korobeynikov schrieb:> Hello Philipp. > >> Why does it need target libraries and binutils? > gcc building process (and llvm-gcc4 as well) includes building of > target-specific stuff including: > > 1. Building crt-support code on several platformsI don't think I need this. I wrote my own crt0.o in assembler.> 2. Building libgcc.a[.so]Why do I need this? Philipp
Apparently Analagous Threads
- [LLVMdev] Byte code portability (was Re: libstdc++ as bytecode, and compiling C++ to C)
- [LLVMdev] Byte code portability (was Re: libstdc++ as bytecode, and compiling C++ to C)
- [LLVMdev] Byte code portability (was Re: libstdc++ as bytecode, and compiling C++ to C)
- [LLVMdev] Byte code portability (was Re: libstdc++ as bytecode, and compiling C++ to C)
- [LLVMdev] Byte code portability (was Re: libstdc++ as bytecode, and compiling C++ to C)