Skip to content

Avoid generating degenerate flow during redundant branch optimization #48609

@kunalspathak

Description

@kunalspathak

Today, we might end up generating degenerate flow during redundant branch optimization. We need to make sure that we don't do that and add an assertion check to make sure that we never have flDupCount > 1 unless it is a switch statement.

We saw #47101 issue because of this and it was fixed in #48607 by making sure assertion prop handles it. But eventually "redundant branch optimization" should not create such flow.

category:cq
theme:flowgraph

Metadata

Metadata

Assignees

Labels

area-CodeGen-coreclrCLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMIin-prThere is an active PR which will close this issue when it is merged

Type

No type

Projects

Status

Done

Relationships

None yet

Development

No branches or pull requests

Issue actions