search for: llvmtupl

...with the idea of mutating the LLVM Tuple in response to compiler options. The steps I'm thinking of for the GNU triple to LLVM Tuple migration are: * Replace any remaining std::string's and StringRef's containing GNU triples with Triple objects. * Split the Triple class into Triple and LLVMTuple classes. Both are identical in implementation at this stage except that Triple has a 'getLLVMTuple()' member function. * Gradually replace Triple's with LLVMTuple's until the public APIs are the only place Triple's are still used. * Change the internals of LLVMTuple to whatever...

On 26 May 2015 at 14:58, Daniel Sanders <Daniel.Sanders at imgtec.com> wrote: > The intention isn't to change the kind of triples/tuples in use by toolchains and users. There's a lot of legacy and inertia to overcome if we try that. The intention is to map the ambiguous/insufficient GNU triples onto an internal representation as early as possible and pass that internal