<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Issue</th>
<td>
<a href=https://github.com/llvm/llvm-project/issues/92724>92724</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>
`DwarfCompileUnit::createAndAddScopeChildren` gobbles stack
</td>
</tr>
<tr>
<th>Labels</th>
<td>
new issue
</td>
</tr>
<tr>
<th>Assignees</th>
<td>
</td>
</tr>
<tr>
<th>Reporter</th>
<td>
workingjubilee
</td>
</tr>
</table>
<pre>
By far the most common stack overflow bug report nowadays for rustc is rustc dying in LLVM while emitting debuginfo. Lately `DwarfCompileUnit::createAndAddScopeChildren` has seemed to acquire the power of recursing on itself and destroying the stack essentially without assistance. People are setting hundreds of megabytes for `RUST_MIN_STACK` to get their code to compile. That's... closer to our resident set size in most executions?
Unlike other reports like #76920 this has been happening with our stock rustc distribution, as far as I can tell, and our bundled LLVM.
</pre>
<img width="1px" height="1px" alt="" src="http://email.email.llvm.org/o/eJycU02PpDYQ_TXmUlrEmP5YDhx6Z9TSKrNRlJnJdWXsArxjXMRVXtL59ZHpiXLPBdAryq_eq2fD7KeI2KvjF3V8qkyWmVK_UXr3cfqRBx8Qq4Hcrf9yg9EkkBlhIRawtCwUgcXYd6CfmMZAGwx5goQrJYFIm3HmxjBSgpRZLHj--HA3HyfwEZ6f__gG2-wDAi5epMAOhzz5OFINz0Yw3ECdmqfNpPGRltUHfIteVHtR7cUmNIKX6C7OvVha8XH2wSWM6tTAbBgYcUEHQmDsn9kn3AWstGECGiGhzYkLKUXwwhhGMNGBQ5ZE-5Dl_7tIZMYo3oRwg83LTFmgGMhiosUafkNaA4JJCIx3KXOOLqHjwrXgZIab4N0QdWp-f3t5_f7t66_fX14vj7-UiYVgQimUPoElhwWxd9E1vM5GlD5zXddgAzGmUqacICF7h1EKL7D_G4u1-5bwL7RZPEVW7VU1T6q53J9vMfh3BJIZ08fGGHZI6fZ86nQDMnveTRwQI8xmXTEWUUX7TstC9v3fjXqW5IedS-lHMLzHxTB8BWsiCIaw49HtvUOOLqDbA1BXrm9d13amwv7h_HB66JrTsa3mHo_YGduN2rr2qPFgOjcO5rNth0Z_Hsau8r1u9KE56qY5t-e2rU17bNrmeHg4tK3FM6pDg4vxoQ7h51JTmirPnLHv9FkfqmAGDLynX-uIG-xFpXW5DKkvPZ-GPLE6NMGz8H-niJeA_f8L5kTDEJDvsapyCv0ssnLp1Felr5OXOQ-1pUXpa2H8eH1aE_1AK0pf9zlZ6euu458AAAD__xQDTLE">