[LLVMdev] [cfe-dev] Target specific info available to Clang (and others)

JF Bastien jfb at google.com
Sat Oct 25 09:38:39 PDT 2014

On Sat, Oct 25, 2014 at 5:01 AM, Renato Golin <renato.golin at linaro.org>

> On 25 October 2014 10:02, David Chisnall <David.Chisnall at cl.cam.ac.uk>
> wrote:
> > To clarify: Are you asking if there's a use case for clang being able to
> generate IR for architectures that it can't generate native code for?  The
> only cases I can think of for this are special targets (SPIR, PNaCl), where
> there isn't a corresponding back end.
> If the only cases are the ones that don't have back-ends, then the
> solution is trivial: create empty back-ends for them that *just*
> contains the target information, and all should behave identical.

I think this is OK for PNaCl.

What David is suggesting is interesting though: what if a target wanted to
have ARM, x86 and MIPS assembly all assembled in a single executable at the
end (not PNaCl's usecase)? It seems like you could just create separate .o
and merge them later, no?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20141025/ff1706ed/attachment.html>

More information about the llvm-dev mailing list