…ng#10725)

fix: Recognize salsa cycles in `thread_result_to_response`

fix: Fix import insertion not being fully cfg aware

…efs-constructor-search

docs: add documentation for find_all_refs constructor search

internal: Restructure some semantics APIs for virtual macro files

refactor: Remove unncessary duplication in highlight_related

Account for `Generate` actions when filtering the allowed ones

fix: Fix manual not containing diagnostics documentation

…ndows

This obviously doesn't work when cross-compiling from Linux.

Split out from: rust-lang#140772

This helps with efforts to deduplicate the `MutVisitor` and the
`Visitor` code. All users of `Visitor`'s methods that have extra
`NodeId` as parameters really just want to visit the id on its
own.

Also includes some methods deduplicated and cleaned up as
a result of this change.

This adds more information to many different codegen options. It should
not add any new guarantees, just document existing behavior.

This disables the f64 minimum/maximum tests for the
arm-unknown-linux-gnueabihf job. The next release will be supporting
cross-compiled doctests, and these tests fail on that platform.

It looks like this was just fixed via
llvm/llvm-project#142170, but I assume that will
not trickle down to our copy of llvm in the next couple of weeks.
Assuming that does get fixed when llvm is updated, then these can be
removed.

cc rust-lang#141087

Obviously `test-float-parse` is a tool like any other in `src/tools`.

Signed-off-by: onur-ozkan <work@onurozkan.dev>

…tter, r=bjorn3

Improve documentation for codegen options

This adds more information to many different codegen options. It should not add any new guarantees, just document existing behavior.

r? bjorn3

…-compiling, r=cuviper

rustc_llvm: add Windows system libs only when cross-compiling from Wi…

…ndows

This obviously doesn't work when cross-compiling from Linux.

Split out from: rust-lang#140772

Fixes the issue described at [#general > Problems while trying to cross compile rustc for windows](https://rust-lang.zulipchat.com/#narrow/channel/122651-general/topic/Problems.20while.20trying.20to.20cross.20compile.20rustc.20for.20windows/with/520508561)

…t_id, r=oli-obk

Add `visit_id` to ast `Visitor`

This helps with efforts to deduplicate the `MutVisitor` and the `Visitor` code. All users of `Visitor`'s methods that have extra `NodeId` as parameters really just want to visit the id on its own.

Also includes some methods deduplicated and cleaned up as a result of this change.

r? oli-obk

Enable triagebot `[concern]` functionality

Documentation at: https://forge.rust-lang.org/triagebot/concern.html
Example at: rust-lang/triagebot#2024

r? Kobzol

…ling, r=oli-obk

Decouple "reporting in deps" from `FutureIncompatibilityReason`

The reason should just be it -- the reason. It never felt right to me that it was also responsible for whatever we include the warning in cargo's reports.

It gets especially unruly if you want to add non-`FutureReleaseError*` warnings which are included in the reports.

I just added a field to `FutureIncompatibleInfo` to control whatever the diagnostic is included in the cargo's reports.

…r=Kobzol

move `test-float-parse` tool into `src/tools` dir

Obviously `test-float-parse` is a tool like any other in `src/tools`.

cc `@tgross35`