[cfe-commits] Ping^2: Fix for bug 11060: configure --target does not work

Sebastian Pop spop at codeaurora.org
Fri Oct 21 15:28:46 PDT 2011

On Fri, Oct 21, 2011 at 5:02 PM, Eric Christopher <echristo at apple.com> wrote:
> Some thinking out loud to open up the discussion:
> I understand this, but I'm just not sure _why_ we want to do such a thing.
> Smaller shipping binaries I suppose?

In my day work, we only care about producing code for one or two targets,
so we build all our compilers enabling only those targets.  As x86 machines
are faster to build things on, we often build the compilers as cross compilers:
we are not interested in producing x86 code out of these toolchains, so x86
is disabled.

> Is it worth the headache of having
> clang understand the cross target but not the native target?

If you are asking me and some other folks building on x86 for embedded
systems: the answer is yes.

> I'm trying
> to avoid the "ship a host-x-target for every target you really want to
> support" headache that comes out of using --target.

I guess that this problem should be answered by those who build and
provide the toolchains: it's their headache ;-)  Now, these folks should
have the option to build a cross compiler that will target a machine
different than host.

Qualcomm Innovation Center, Inc is a member of Code Aurora Forum

More information about the cfe-commits mailing list