search for: basicaawrapperpass

...But now there is a reason to make them match, so that we don't have to touch every single test that uses `opt`. There are a couple of names that don't match though, for example the "basic alias analysis" pass is named "basicaa" under the legacy PM INITIALIZE_PASS_BEGIN(BasicAAWrapperPass, "basicaa", "Basic Alias Analysis (stateless AA impl)", true, true) but named "basic-aa" under the NPM FUNCTION_ALIAS_ANALYSIS("basic-aa", BasicAA()) . Almost all the other AA passes have a dash in them so I think it makes sense to renam...

...so that we don't have to touch every single test >> that uses `opt`. >> >> There are a couple of names that don't match though, for example the >> "basic alias analysis" pass is named "basicaa" under the legacy PM >> INITIALIZE_PASS_BEGIN(BasicAAWrapperPass, "basicaa", >>                       "Basic Alias Analysis (stateless AA impl)", >> true, true) >> but named "basic-aa" under the NPM >> FUNCTION_ALIAS_ANALYSIS("basic-aa", BasicAA()) >> . Almost all the other AA passes have a d...

...match, so that we don't have to touch every single test that uses `opt`. >>> >>> There are a couple of names that don't match though, for example the "basic alias analysis" pass is named "basicaa" under the legacy PM >>> INITIALIZE_PASS_BEGIN(BasicAAWrapperPass, "basicaa", >>> "Basic Alias Analysis (stateless AA impl)", true, true) >>> but named "basic-aa" under the NPM >>> FUNCTION_ALIAS_ANALYSIS("basic-aa", BasicAA()) >>> . Almost all the other AA passes ha...

...here? Does it include removing the -passes option used by > the NPM? > > >> >> There are a couple of names that don't match though, for example the >> "basic alias analysis" pass is named "basicaa" under the legacy PM >> INITIALIZE_PASS_BEGIN(BasicAAWrapperPass, "basicaa", >> "Basic Alias Analysis (stateless AA impl)", true, >> true) >> but named "basic-aa" under the NPM >> FUNCTION_ALIAS_ANALYSIS("basic-aa", BasicAA()) >> . Almost all the other AA passes have a da...

...;Function Alias Analysis Results' even though the latter > depends on the former (at least AFAICT by looking > at lib/Analysis/AliasAnalysis.cpp)? > > > > As far as I can tell later passes such as scheduling typically depend on > AAResultsWrapperPass which in turn depend on BasicAAWrapperPass (which in > my case also depend on LazyValueInfoWrapperPass). When scheduling needs to > query aliasing it uses its AAResults handle but this may then use its > BasicAA handle which may use its LVI handle and now the problem is that > according to -debug-pass=Executions the latter two h...

Hi, Looking at the output of e.g. llc -mtriple=x86_64-unknown-linux-gnu test/CodeGen/X86/pre-coalesce.ll -debug-pass=Executions Why is it that 'Basic Alias Analysis (stateless AA impl)' is freed much earlier than 'Function Alias Analysis Results' even though the latter depends on the former (at least AFAICT by looking at lib/Analysis/AliasAnalysis.cpp)? Thanks! -Markus

The management of passes in the legacy PM is ... highly confusing. Do you have a specific problem you're trying to solve or a specific question? On Thu, Dec 27, 2018 at 6:47 AM Markus Lavin via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hi, > > > Looking at the output of e.g. > > > llc -mtriple=x86_64-unknown-linux-gnu test/CodeGen/X86/pre-coalesce.ll >