 /// Clients that need to handle the non-canonical triples that users often
 /// specify should use the normalize method.
 ///
-/// See autoconf/config.guess for a glimpse into what configuration names
+/// See autoconf/config.guess for a glimpse into what target triples
 /// look like in practice.
 ///
 /// This is a port of https://github.com/apple/swift-llvm/blob/stable/include/llvm/ADT/Triple.h

private func parseBPFArch<S: StringProtocol>(_ archName: S) -> Triple.Arch {
  switch archName {
  case "bpf":
    fatalError("Unimplemented - need to determine host endianness")
  case "bpf_be", "bpfeb":
    return .bpfeb
  case "bpf_le", "bpfel":

/// Helper for working with target triples.
///
/// Target triples are strings in the canonical form:
///   ARCHITECTURE-VENDOR-OPERATING_SYSTEM
/// or
///   ARCHITECTURE-VENDOR-OPERATING_SYSTEM-ENVIRONMENT
