The `data-layout` field is no longer required, but the `os` field is

The `data-layout` field  was made optional in 958d5638254958ea42652de7444b63f2e67e7fe3. The `os` field is always required.

diff --git a/src/librustc_back/target/mod.rs b/src/librustc_back/target/mod.rs
index 266144f61de177191f7242a0ee3cb1f6234d5eca..ab5a63a5470d25438b670327470b8962cb7a7814 100644 (file)
--- a/src/librustc_back/target/mod.rs
+++ b/src/librustc_back/target/mod.rs
@@ -40,8 +40,8 @@
 //! this module defines the format the JSON file should take, though each
 //! underscore in the field names should be replaced with a hyphen (`-`) in the
 //! JSON file. Some fields are required in every target specification, such as
-//! `data-layout`, `llvm-target`, `target-endian`, `target-pointer-width`, and
-//! `arch`. In general, options passed to rustc with `-C` override the target's
+//! `llvm-target`, `target-endian`, `target-pointer-width`, `arch`, and
+//! `os`. In general, options passed to rustc with `-C` override the target's
 //! settings, though `target-feature` and `link-args` will *add* to the list
 //! specified by the target, rather than replace.