[cfe-dev] First shot at Bug 4127 - The clang driver should support cross compilation
James Molloy
James.Molloy at arm.com
Tue Jan 10 02:51:30 PST 2012
Certainly a good idea, and probably better than having two different formats.
I like it (and if that's the only issue you have with my über plan, I'm a happy man!)
Cheers,
James
-----Original Message-----
From: cfe-dev-bounces at cs.uiuc.edu [mailto:cfe-dev-bounces at cs.uiuc.edu] On Behalf Of David Chisnall
Sent: 10 January 2012 10:42
To: James Molloy
Cc: 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
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).
David
-- Sent from my brain
_______________________________________________
cfe-dev mailing list
cfe-dev at cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
-- 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