[cfe-dev] Using clang/LLVM components in conventional apps?

[Douglas Gregor]

On Jun 26, 2009, at 8:24 AM, Dallman, John wrote:

> Sebastian Redl [mailto:sebastian.redl at getdesigned.at] wrote:
>
>> It's simpler, actually. The dylib doesn't contain LLVM bitcode
> anymore;
>> it's a perfectly normal machine code object. It should be (according
> to
>> the project goals) 100% binary compatible with GCC-compiled code. So
>> there should be no compatibility issues at all.
>
> OK. I was under the impression the one of the points of LLVM was that
> it could target the hardware at run-time: some of the examples of how
> it's used for OpenGL and so on seem to work that way?

One can use LLVM that way, but it's not the default for Clang.

> Presumably here it's just being used as a step along the route from
> source to binary: would clang produce conventional .o files, or
> don't you get ordinary machine code until you link?

Clang produces conventional .o files that are 100% binary-compatible  
with GCC.

	- Doug