[cfe-dev] Rename -ccc-host-triple into -ccc-target-triple
Sebastian Pop
spop at codeaurora.org
Wed Jan 4 13:02:48 PST 2012
On Wed, Jan 4, 2012 at 2:29 PM, David Chisnall <csdavec at swan.ac.uk> wrote:
> On 4 Jan 2012, at 19:58, Sebastian Pop wrote:
>
>> Hi,
>>
>> On Tue, Dec 27, 2011 at 1:55 PM, Sebastian Pop <spop at codeaurora.org> wrote:
>>> Hi,
>>>
>>> I would like to rename -ccc-host-triple into -ccc-target-triple.
>>>
>>> The host (that is the machine on which clang is running) cannot be
>>> changed, and what this flag does is that it changes the llvm backend
>>> clang will use to produce code, that is called the target machine.
>>>
>>> Does anybody see a reason to keep the old misleading name?
>>>
>>
>> I would like to have some comments on this change:
>> ok to commit, or hold on?
>
> I am definitely in favour of less confusing names. It took me a while to understand what these mean. Apparently gcc uses three terms:
>
> - build (for the system building the compiler)
> - target (for the system that the compiler is built to run on)
> - host (for the system that the code built with the compiler is build to run on)
Really?
Can you send out a pointer to the documentation page that you were reading?
I have never seen these definitions for target and host in GCC.
In the autoconf documentation you also have it the other way around,
please read:
http://airs.com/ian/configure/configure_5.html
"The system on which the tools will run is called the host system.
The system for which the tools generate code is called the target system."
> This is a bit confusing, but unfortunately this terminology also seems to have made its way into the configure scripts. The autoconf documentation uses these three and when you do cross-building with autoconf you specify the host, not the target. My worry is that if we start using target to mean what GCC users call host then this will confuse people (well, more than they are already confused by the GNU project getting host and target the wrong way around).
>
> Perhaps we could just rename the option -ccc-triple? Neither a -ccc-build-triple nor a -ccc-target-triple (in GCC terminology) would make sense, so specifying host / target here seems redundant, and not specifying anything means that we won't introduce confusion from the what-sane-people-thing and what-gcc-developer-say mismatch.
-ccc-triple is fine with me.
Sebastian
--
Qualcomm Innovation Center, Inc is a member of Code Aurora Forum
More information about the cfe-dev
mailing list