[llvm-commits] [PATCH llvm, clang llvm-gcc] Add TCE targt to LLVM and CLANG support for generating bytecode to TCE architecture.

Eli Friedman eli.friedman at gmail.com
Mon Aug 17 04:39:55 PDT 2009

2009/8/17 Mikael Lepistö <lepisto.mikael at gmail.com>:
> Actually we would liked to add the target to llvm because, otherwise we
> cannot set correct target triplet and data layout information to bitcode
> which is generated with llvm-gcc cross-compiler (currently cross-compiler
> puts just mips data layout and triple even if code is compiled differently).

Ah, I wasn't aware of that restriction; that makes the whole thing
make a lot more sense, although it's still not pretty.

>> As this applies to TCE-clang-target-rc3.patch: It's not directly
>> affected by the other patch, but it's hard to justify adding the
>> target to clang when it's not usable by anyone else.
> I'm not sure how it would be even possible to make it more usable for anyone
> else, since the TCE TTA application specific processor is developed by us
> and all the design tools as well.
> Design tools are publicly available (MIT licence) and takes program input in
> llvm bitcode format. So everyone who is developing TCE application specific
> processors and software for them can use the clang target.

Ah, so the tools are publicly available... I missed that bit.  Since
it isn't too invasive, I guess it's okay... but it would be nice to
add a comment with a quick description, because otherwise it isn't
obvious why clang supports a target which LLVM can't generate code
for.  Also, please send it separately to cfe-commits to see if anyone
else has comments.


More information about the llvm-commits mailing list