[LLVMdev] Target specific info available to Clang (and others)
rafael.espindola at gmail.com
Fri Oct 24 11:17:22 PDT 2014
> I mean, we have three issues:
> 1. It's nice to have Clang generate IR for all archs on any arch
> 2. We need target info to do that, currently Clang duplicates everything
> 3. We don't want to bloat native binaries in restricted environments
> I'm beginning to think that the "nice" feature 1 is not worth the two
> big problems 2 and 3. If we tie Clang builds with back-end builds and
> force it not to have support for other arches (because the info isn't
> available if you don't build its back-end), than all that info can
> still be public and not completely bloat the final libraries.
> Is there any stronger reason why Clang must be able to generate IR for
> any arch on any arch?
Last time the idea of just using lib/Target was raised Alp mentioning
having a use case for the current ability.
More information about the llvm-dev