Modern processors predict the target(s) of an indirect branche regardless of the size of any jump table used to glean its target address. Rather, branch predictors typically use resources limited by the number of actual targets that occur at run time.
This patch changes the semantics of the options min-jump-table-entries and max-jump-table-size to use the number of different targets instead of the number of entries in a jump table. Thus, the are now renamed to min-jump-table-cases and max-jump-table-cases, respectively.
Before, when max-jump-table-cases was specified, it could happen that cluster jump tables could have targets used repeatedly, but typically the same length. With this patch, tables may have different lengths, but typically the same number of unique targets.