Fix rust-lang#58857.

Fix rust-lang#58815.

Fix rust-lang#56472.

…on for Option

The example had a potential race condition that would still pass the test.
If the thread which was supposed to modify it's own thread local was slower than the instruction to
modify in the main thread, then the test would pass even in case of a failure.
This is would be minor if the child thread was waited for since it check using an `assert_eq` for
the same thing, but vice versa.
However, if the `assert_eq` failed this would trigger a panic, which is not at all caught by the
example since the thread is not waited on.

Signed-off-by: benaryorg <binary@benary.org>

)

This code no longer ICEs, and @yodaldevoid found that it was fixed by
commit fe5710a. While that added a similar test, we can explicitly test
this reproducer too.

Closes rust-lang#50582.

Fix rust-lang#58712.

Was then able to the minimise the reproduction a little further.

JSBackend is implied when building the emscripten backend, and not available for the standard llvm backend.  This commit also puts the example config in sync with the defaults in src/bootstrap/native.rs

(Update: Fixed test; revision is meant to introduce compile-failure, w/o ICE.)

…bug.

(It is possible that there is a more fundamental invariant being
violated, in terms of the `check_type_defn` code assuming that lifting
to tcx will always succeed. But I am unaware of any test input that
hits this that isn't already type-incorrect in some fashion.)

`-Z treat-err-as-bug=0` will cause `rustc` to panic after the first
error is reported. `-Z treat-err-as-bug=2` will cause `rustc` to
panic after 3 errors have been reported.

Add FreeBSD armv6 and armv7 targets

On return type `impl Trait` for block with no expr point at last semi

Partial solution, doesn't actually validate that the last statement in the function body can satisfy the trait bound, but it's a good incremental improvement over the status quo.

```
error[E0277]: the trait bound `(): Bar` is not satisfied
  --> $DIR/impl-trait-return-trailing-semicolon.rs:3:13
   |
LL | fn foo() -> impl Bar {
   |             ^^^^^^^^ the trait `Bar` is not implemented for `()`
LL |     5;
   |      - consider removing this semicolon
   |
   = note: the return type of a function must have a statically known size
```

Partially addresses rust-lang#54771.

…-distribution, r=Mark-Simulacrum

Add librustc and libsyntax to rust-src distribution.

Fixes rust-lang#58268.

Make the Entry API of HashMap<K, V> Sync and Send

Fixes rust-lang#45219

…rochenkov

Expand where negative supertrait specific error is shown

Fix rust-lang#58857.

r? @petrochenkov

Suggest removal of `&` when borrowing macro and appropriate

Fix rust-lang#58815.

Suggest appropriate code for unused field when destructuring pattern

Fix rust-lang#56472.

Remove stray ` in the docs for the FromIterator implementation for Option

…, r=alexcrichton

race condition in thread local storage example

The example had a potential race condition that would still pass the test.
If the thread which was supposed to modify it's own thread local was slower than the instruction to
modify in the main thread, then the test would pass even in case of a failure.
This is would be minor if the child thread was waited for since it check using an `assert_eq` for the
same thing, but vice versa.
However, if the `assert_eq` failed this would trigger a panic, which is not at all caught by the
example since the thread is not waited on.

Signed-off-by: benaryorg <binary@benary.org>

… r=Zoxc

Monomorphize generator field types for debuginfo

Fixes rust-lang#58888

r? @Zoxc

…t, r=alexcrichton

Regression test for rust-lang#58435.

Fix rust-lang#58435

…ess-test, r=petrochenkov

Regression test for rust-lang#58813

Fix rust-lang#58813

Fix release note problems noticed after merging.

Cherry picked from stable branch.

…e, r=petrochenkov

Regression test added for an async ICE.

Regression test for rust-lang#57084 (as suggested in issue).

Add an explicit test for issue rust-lang#50582

This code no longer ICEs, and @yodaldevoid found that it was fixed by
commit fe5710a. While that added a similar test, we can explicitly test
this reproducer too.

Closes rust-lang#50582.

Make the lifetime parameters of tcx consistent.

I have implemented `codegen_allocator` for my backend, but I've had to make a small change to its signature in `ExtraBackendMethods`. I wonder if this change is justified, or if it is too specific to my use case to be useful to anyone else.

`write_metadata` and `codegen_allocator` are both called from `codegen_crate` (in `librustc_codegen_ssa/base.rs`), and they both receive the same `tcx` as an argument:

https://github.com/rust-lang/rust/blob/c196097e588b05e86b5ce6de992b2a6e6a7027bd/src/librustc_codegen_ssa/base.rs#L555-L557

and:

https://github.com/rust-lang/rust/blob/c196097e588b05e86b5ce6de992b2a6e6a7027bd/src/librustc_codegen_ssa/base.rs#L640-L642

However, `codegen_allocator` accepts a `TyCtxt` with any lifetime parameters (`tcx: TyCtxt<'_, '_, '_>`), while `write_metadata` requires that the `tcx` argument is of type `TyCtxt<'b, 'gcx, 'gcx>`. In my implementation, I've found that it's necessary for `tcx` in `codegen_allocator` to also have the `<'b, 'gcx, 'gcx>` lifetime parameters.

Have I misunderstood the purpose of the parameters of `TyCtxt`? I've read [here](https://rust-lang.github.io/rustc-guide/ty.html) that the last two parameters only need to be distinct if the function needs to be used during type inference, but I don't think that is the case here.

…rkor

Elide invalid method receiver error when it contains TyErr

Fix rust-lang#58712.

…hton

Remove JSBackend from config.toml

JSBackend is implied when building the emscripten backend, and not available for the standard llvm backend.  This commit also puts the example config in sync with the defaults in src/bootstrap/native.rs

Add self to mailmap

On incorrect cfg literal/identifier, point at the right span

CC rust-lang#58462

libstd: implement Error::source for io::Error

…type-ice, r=petrochenkov

delay_span_bug in wfcheck's ty.lift_to_tcx unwrap

Fix rust-lang#58158

…oli-obk

Teach `-Z treat-err-as-bug` to take a number of errors to emit

`-Z treat-err-as-bug` will cause `rustc` to panic after the first error is reported, like previously. `-Z treat-err-as-bug=2` will cause `rustc` to panic after 2 errors have been reported.

Fix rust-lang#58983.

…trochenkov

Add a test for invalid const arguments

Closes rust-lang#58811.