An analysis of GCC switch lowering shows that a large number of cases does not automatically produce a jump table. Value spacing, comparison cost, and optimization for speed or code size influence the choice and combination of comparison trees, bit tests and jump tables. One example contains regularly spaced values that could be simplified by division, but the compiler does not discover that transformation. This is a 2024 examination of particular compiler output, not a new release or a guarantee for every target CPU. Performance-sensitive branches should be assessed using actual compiler options, generated assembly and input distributions, not source-code appearance alone.