GCCRS gets killed (SIGKILL) when compiling function with massive if-else branches

Summary

When compiling a Rust function containing a large number of if-else branches (e.g., several thousand), GCCRS exceeds processing time and is terminated by SIGKILL, while Rustc compiles successfully with only a dead code warning.

Reproducer

I tried this code:

#![crate_type = "rlib"]

fn banana(v: &str) -> u32 {
    if v == "1" { 1 }
    else if v == "2" { 2 }
    // ... Hundreds/Thousands of similar branches ...
    else if v == "5205" { 5205 }
    else { 5206 }
}

Does the code make use of any (1.49) nightly feature ?

• Nightly

Godbolt link

https://godbolt.org/z/Gsae38rae

Actual behavior

GCCRS fails to complete compilation (SIGKILL), indicating a severe performance bottleneck or infinite loop in the compiler.

Expected behavior

GCCRS should handle large but syntactically valid functions gracefully, possibly with a warning about code size or performance, but not crash.

GCC Version

14.0.1

Start by reproducing the SIGKILL with the linked Godbolt example or the several-thousand-branch function, then compare GCCRS and rustc behavior. Trace the compiler stages processing the chained if-else expressions and identify where compilation time or memory grows unexpectedly. Done means the reproducer completes without being killed and existing compiler tests cover the regression.