Hi,
I have written new dummy target to llvm-gcc for our processor
architecture,
which contains basically only the information which is necessary to
generate
llvm byte code. I could check tomorrow in work, which parts of llvm-
gcc had to
be altered for our "tce-llvm-gcc" cross-compiler.
I also hardcoded compiler to use llvm-ld and llvm-as as it's
bintools, for
being able to link and compile e.g. newlib to bytecode library.
Is this basically the same thing that you are looking for?
Mikael Lepistö
On Oct 15, 2007, at 1:04, Anton Korobeynikov wrote:
> Boris,
>
>> Yes, I know that. configure --target=a-b-c will fail because there
>> is no such stuff known in gcc. So, what is the answer/consequence? An
>> existing gcc back-end for architecture "a" is a precondition
for a
>> LLVM back-end for architecture "a"?
> No. This is requirement of using gcc as a frontend. This looks pretty
> weird, but it is: frontend should know some details about your target
> architecture (for example, pointer type, and much more). However, you
> might try to create "blank" gcc arch and try to fill all
necessary
> bits.
> Dunno, how hard it is.
>
>> Is there another fully working C front-end for LLVM?
> Not yet. However, I think, you can try clang and try to find what's
> not
> working for you.
>
> --
> With best regards, Anton Korobeynikov.
>
> Faculty of Mathematics & Mechanics, Saint Petersburg State University.
>
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev