On 6/15/2021 12:04 AM, Richard Biener wrote:
On Tue, 15 Jun 2021, Aldy Hernandez wrote:
On 6/14/21 4:04 PM, Richard Biener wrote:
The same issue that arises in PR100934 can happen in the backward
threader now (Aldy?) - we eventually run into mark_irreducible_loops
for non-FSM thread paths
On 6/15/21 10:27 AM, Richard Biener wrote:
On Tue, 15 Jun 2021, Richard Biener wrote:
On Tue, 15 Jun 2021, Aldy Hernandez wrote:
On 6/14/21 4:04 PM, Richard Biener wrote:
The same issue that arises in PR100934 can happen in the backward
threader now (Aldy?) - we eventually run into mark
On Tue, 15 Jun 2021, Richard Biener wrote:
> On Tue, 15 Jun 2021, Aldy Hernandez wrote:
>
> >
> >
> > On 6/14/21 4:04 PM, Richard Biener wrote:
> > > The same issue that arises in PR100934 can happen in the backward
> > > threader now (Aldy?) - we eventually run into mark_irreducible_loops
> >
On Tue, 15 Jun 2021, Aldy Hernandez wrote:
>
>
> On 6/14/21 4:04 PM, Richard Biener wrote:
> > The same issue that arises in PR100934 can happen in the backward
> > threader now (Aldy?) - we eventually run into mark_irreducible_loops
> > for non-FSM thread paths checking for paths crossing irred
On 6/14/21 4:04 PM, Richard Biener wrote:
The same issue that arises in PR100934 can happen in the backward
threader now (Aldy?) - we eventually run into mark_irreducible_loops
for non-FSM thread paths checking for paths crossing irreducible
region boundaries.
I haven't been following the ab
The same issue that arises in PR100934 can happen in the backward
threader now (Aldy?) - we eventually run into mark_irreducible_loops
for non-FSM thread paths checking for paths crossing irreducible
region boundaries.
The following thus initializes irreducible regions and makes
irreducible region
