about summary refs log tree commit diff
path: root/compiler/rustc_codegen_llvm/src/llvm/mod.rs
diff options
context:
space:
mode:
authorMatthias Krüger <matthias.krueger@famsik.de>2022-02-26 07:52:44 +0100
committerGitHub <noreply@github.com>2022-02-26 07:52:44 +0100
commit648a8e314ad28293b721888839c3ac6a0184cf22 (patch)
tree509d8bc2da1015a7950ae99be0405e79629cdc0c /compiler/rustc_codegen_llvm/src/llvm/mod.rs
parentd6ca3885842d5ad282d9631fb4c94a1ba9227434 (diff)
parent4d89292785653e399512d85f95a9870836ec9632 (diff)
downloadrust-648a8e314ad28293b721888839c3ac6a0184cf22.tar.gz
rust-648a8e314ad28293b721888839c3ac6a0184cf22.zip
Rollup merge of #94306 - Mark-Simulacrum:dom-fixups, r=jackh726
Avoid exhausting stack space in dominator compression

Doesn't add a test case -- I ended up running into this while playing with the generated example from #43578, which we could do with a run-make test (to avoid checking a large code snippet into tree), but I suspect we don't want to wait for it to compile (locally it takes ~14s -- not terrible, but doesn't seem worth it to me). In practice stack space exhaustion is difficult to test for, too, since if we set the bound too low a different call structure above us (e.g., a nearer ensure_sufficient_stack call) would let the test pass even with the old impl, most likely.

Locally it seems like this manages to perform approximately equivalently to the recursion, but will run perf to confirm.
Diffstat (limited to 'compiler/rustc_codegen_llvm/src/llvm/mod.rs')
0 files changed, 0 insertions, 0 deletions