search for: requiredanalysispass

...t always a good flag to detect PGO cases [3] or we tend to build pass pipelines before examining the code (or without propagating enough info down) [4]. Proposed approach - Cache PSI right after the profile summary in the IR is written in the pass pipeline [5]. This would avoid the need to insert RequiredAnalysisPass for PSI before each non-module pass that needs it. PSI can be technically invalidated but unlikely. If it does, we insert another RequiredAnalysisPass [6]. - Conditionally insert RequireAnalysisPass for BFI, if PGO, right before each loop pass that needs it. This doesn't seem avoidable becaus...

...end to build pass pipelines before examining the code (or >> without propagating enough info down) [4]. >> >> Proposed approach >> >> - Cache PSI right after the profile summary in the IR is written in the >> pass pipeline [5]. This would avoid the need to insert RequiredAnalysisPass >> for PSI before each non-module pass that needs it. PSI can be technically >> invalidated but unlikely. If it does, we insert another RequiredAnalysisPass >> [6]. >> >> - Conditionally insert RequireAnalysisPass for BFI, if PGO, right before >> each loop pass...

...info down) [4]. >>> >>> Proposed approach >>> >>> - Cache PSI right after the profile summary in the IR is >>> written in the pass pipeline [5]. This would avoid the >>> need to insert RequiredAnalysisPass for PSI before each >>> non-module pass that needs it. PSI can be technically >>> invalidated but unlikely. If it does, we insert another >>> RequiredAnalysisPass[6]. >>> >>> - Conditionally insert RequireA...

...O cases > [3] or we tend to build pass pipelines before examining the code (or > without propagating enough info down) [4]. > > Proposed approach > > - Cache PSI right after the profile summary in the IR is written in the > pass pipeline [5]. This would avoid the need to insert RequiredAnalysisPass > for PSI before each non-module pass that needs it. PSI can be technically > invalidated but unlikely. If it does, we insert another RequiredAnalysisPass > [6]. > > - Conditionally insert RequireAnalysisPass for BFI, if PGO, right before > each loop pass that needs it. This does...

...;> >>>> Proposed approach >>>> >>>> - Cache PSI right after the profile summary in the >>>> IR is written in the pass pipeline [5]. This would >>>> avoid the need to insert RequiredAnalysisPass for >>>> PSI before each non-module pass that needs it. PSI >>>> can be technically invalidated but unlikely. If it >>>> does, we insert another RequiredAnalysisPass[6]. >>>> >>>>...

...>> >>>>> - Cache PSI right after the profile summary in >>>>> the IR is written in the pass pipeline [5]. >>>>> This would avoid the need to insert >>>>> RequiredAnalysisPass for PSI before each >>>>> non-module pass that needs it. PSI can be >>>>> technically invalidated but unlikely. If it >>>>> does, we insert another RequiredAnalysisPass[6]. >>>>>...