search for: profileloaderpassid

...t: If I use AU.addRequired<ProfileInfo>() in SelectionDAGISel.cpp the wrong ProfileInfo is used. It uses the "No ProfileInfo" implementation if ProfileInfo but not the one from ProfileInfoLoaderPass. (Which is immediately discarded after creation.) When I use AU.addRequiredID(ProfileLoaderPassID) I get assertions that a normal constructor is not available. Interesting enough its not the ProfileInfoLoader constructor thats misssing but the one from MachineFunctionAnalysis, which indeed has none. This raises the question why different passes are loaded (in a different order) when I use...

Hi, Devang Patel wrote: > On Tue, Nov 17, 2009 at 9:03 AM, Andreas Neustifter > <astifter-llvm at gmx.at> wrote: > >> Okay, so the ProfileInfoLoader is working, but when I examine the executions more closely I see that the ProfileInfo generated by the ProfileInfoLoader is immediately discarded, when the SelectionDAGISel kicks in the "No Profile Info"-Implementation

...in the list of invalidated passes. Attached patch adds debug output for _all_ invalidated passes. I will commit this in the next days if there are no objections. On 11/20/2009 04:30 PM, Anton Korobeynikov wrote: > > Andreas Neustifter wrote: >> >> When I use AU.addRequiredID(ProfileLoaderPassID) I get assertions >> that a normal constructor is not available. Interesting enough its >> not the ProfileInfoLoader constructor thats misssing but the one from >> MachineFunctionAnalysis, which indeed has none. > > Right. You cannot schedule any pass IR-level pass afte...

On Fri, Nov 20, 2009 at 6:54 AM, Andreas Neustifter <astifter-llvm at gmx.at> wrote: > > If I use  AU.addRequired<ProfileInfo>() in SelectionDAGISel.cpp the > wrong ProfileInfo is used. It uses the "No ProfileInfo" implementation > if ProfileInfo but not the one from ProfileInfoLoaderPass. (Which is > immediately discarded after creation.) > You need to