[cfe-dev] First shot at Bug 4127 - The clang driver should support cross compilation

James Molloy James.Molloy at arm.com
Tue Jan 10 03:49:14 PST 2012

Custom setups have two options in this case.

They must add their setup to the JSON target DB. If they want to, then can then recompile and clang would parse that and create C++ classes to do the work. If not, they could distribute that JSON file and Clang would read it at runtime and do the same job, just slightly slower.

-----Original Message-----
From: Konstantin Tokarev [mailto:annulen at yandex.ru]
Sent: 10 January 2012 11:34
To: David Chisnall
Cc: James Molloy; Sebastian Pop; cfe-dev at cs.uiuc.edu Developers; clang-commits at cs.uiuc.edu
Subject: Re: [cfe-dev] First shot at Bug 4127 - The clang driver should support cross compilation

10.01.2012, 14:41, "David Chisnall" <theraven at sucs.org>:
> On 10 Jan 2012, at 10:00, James Molloy wrote:
>>   * This can take two forms - hard-baked and JSON. The hard-baked version I see being a tablegen file similar (as possible) to the JSON representation, which is compiled into Clang for speed.
> Is there any reason why you can't create a tool that parses the JSON and emits a C++ class so that it can be exactly the same for the cases that don't require any custom executable logic?  This would make prototyping new platforms a lot easier, since it would mean that you'd just poke the JSON until it worked and then add it to the list of JSON files to be transformed into C++ in the default build when it was ready (and people shipping clang for their obscure platform could just add it as part of their default build, even if it were of no interest to anyone else).

What about custom cross-toolchain setups? They would require recompilation?


-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium.  Thank you.

More information about the cfe-dev mailing list