================
@@ -199,6 +199,7 @@ class Triple {
SUSE,
OpenEmbedded,
Intel,
+ WALI,
----------------
dschuff wrote:
Yeah, triples are well known to be not really sufficient for capturing
everything you'd want to know about a compilation, all the aspects of the
architecture, set of syscalls available, and ABI; and there's a messy history
of vendors with either the same or different ABIs. Since this is adding a new
OS and ABI to the set of triples, if an RFC is the right way to go, then we
should do that. If the consensus is that we should do something other than just
add a vendor, is it too late to modify rustc to agree with LLVM and clang?
https://github.com/llvm/llvm-project/pull/156087
_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
