Ok, I can't use `std` in doc-links, only in doc-tests.  Try 7...

…ding on Windows."

This reverts commit 74a39a3.

When `rustc` is invoked with the `--print` argument, we don't actually
generate any code (unless it's the `native-static-libs` option). So we
don't need to error our in this case since there's no risk of generating
either LLVM assertions or corrupted binaries.

…uity hint

Change some tests to `check-pass` that are only testing name resolution.

`normalize-stdout-test` removes the need for Make, and it can be updated
with `--bless` this way

rust-lang#60532

Per rust-lang#59356 it is expected that the interpretation of the bitmask depends
on target endianness.

Closes rust-lang#59356

…acrum

Fix hyperlinks in From impls between Vec and VecDeque

I'd been trying to link them, but apparently actually just added brackets: <https://doc.rust-lang.org/nightly/std/collections/struct.VecDeque.html#impl-From%3CVec%3CT%3E%3E>

~~This reverts commit 5168f5d.~~

~~(I'd previously tried to make relative links, but those failed linkcheck because the types are exported at different levels.  So just skip the links -- they're already linked in the function signature anyway.)~~

This makes the links now work.

 Only error about MSVC + PGO + unwind if we're generating code

In rust-lang#61853, we changed the error when using PGO & MSVC toolchain & panic=unwind into a warning. However, in the compiler team meeting on 2019-07-11, we found that not everybody was in favor of that change because of the possibility of broken binaries.

This PR reverts that change so this is again an error. However, to work around an [issue the Firefox team is having](rust-lang#61002 (comment)), we will only emit the error if we're actually supposed to generate a binary. If the `rustc` is invoked with `--print` arguments (which means that no binary will actually be emitted), then we won't emit the error because there is not a possibility of the issue occurring.

cc @EricRahm @nikomatsakis @pnkfelix @Centril

Check that trait is exported or public before adding hint

Closes rust-lang#62194.

This PR checks the `AccessLevels` of a trait to check whether adding the intercrate ambiguity hint is valid or not.

I am unsure of both the use of `.unwrap()` as well as removing hints for [downstream *and* [upstream](https://github.com/rust-lang/rust/blob/92b0f52584c9375505ecdefdd7855b93a5919d51/src/librustc/traits/select.rs#L112-L142).

Update the help message on error for self type

Fix rust-lang#62609

…nas-schievink

Fix repeated wording in slice documentation

Changes `of the slice of the slice` to `of the slice` in the chunk- and friends documentation of slices

…ochenkov

Consolidate hygiene tests

Some general clean-up extracted out from another PR

Remove last use of mem::uninitialized from std::io::util

Addresses rust-lang#62397 for std::io::util

Add missing link to Infallible in TryFrom doc

update data_layout and features for armv7-wrs-vxworks

Document link_section arbitrary bytes

Closes rust-lang#60633.

Disable Z3 in LLVM build

Avoid building LLVM with Z3 if it happens to be installed.

Fixes rust-lang#62750.

r? @alexcrichton

…_compiler_messages_p7, r=alexreg

normalize use of backticks in compiler messages for librustc/lint

rust-lang#60532

Disable simd_select_bitmask test on big endian

Per rust-lang#59356 it is expected that the interpretation of the bitmask depends
on target endianness.

Closes rust-lang#59356

…sion, r=eddyb

Self-referencial type now called a recursive type

As per Boat's suggestion - rust-lang#62539, this makes the error message clearer.

Emit artifact notifications for dependency files

Emit `dep-info` artifact notifications for `.d` files.