diff options
| author | bors <bors@rust-lang.org> | 2023-06-16 05:48:08 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2023-06-16 05:48:08 +0000 |
| commit | 0966f3202d1e811cd3aa35ac876b61a211b4819a (patch) | |
| tree | 8a86fac61f1344e880094a0d7205ff1a7cc19cb2 /compiler/rustc_codegen_gcc | |
| parent | c84d5e7078435a0ddd8770c3530fe7fdbf026ec4 (diff) | |
| parent | 44789b626b7b03cd57edab04fd6ebaafe349e954 (diff) | |
| download | rust-0966f3202d1e811cd3aa35ac876b61a211b4819a.tar.gz rust-0966f3202d1e811cd3aa35ac876b61a211b4819a.zip | |
Auto merge of #112673 - scottmcm:enough-stack, r=compiler-errors
Add an `ensure_sufficient_stack` to `LateContextAndPass::visit_expr` This is [apparently](https://rust-lang.zulipchat.com/#narrow/stream/182449-t-compiler.2Fhelp/topic/.60-alt.60-only.20failures.3F/near/365396801) where it's busting stack in #112238, and the comments for `ensure_sufficient_stack` say that > E.g. almost any call to visit_expr or equivalent can benefit from this. So this seems like a reasonable change. Hopefully it'll keep this from happening in other places too -- https://github.com/rust-lang/rust/pull/111818#issuecomment-1585023914 hit something similar when updating a lint (bors failure is https://github.com/rust-lang-ci/rust/actions/runs/5199591324/jobs/9377196369), so with any luck this will keep small permutations of things from tripping over the limit.
Diffstat (limited to 'compiler/rustc_codegen_gcc')
0 files changed, 0 insertions, 0 deletions