search for: pgoedg

...t change the profile, but introducing a conditional branch invalidates the profile. The issue I would like to address is which transformations should we allow as safe transformations and how should we update the internal path profile data structures if we allow this at all. > > + Verify with PGOEdge info ? > Ditto. Verification with PGOEdge info implies that the edge frequencies derived from path profiles and via instrprof should be equal. > > + Handle setjmp, longjmp, early program termination, noreturn calls > How do you handle indirect calls? No special handling of indire...

...itional branch invalidates the >> profile. The issue I would like to address is which transformations should >> we allow as safe transformations and how should we update the internal path >> profile data structures if we allow this at all. >> >> > > + Verify with PGOEdge info ? >> >> > Ditto. >> >> Verification with PGOEdge info implies that the edge frequencies derived >> from path profiles and via instrprof should be equal. >> >> > > + Handle setjmp, longjmp, early program termination, noreturn calls >> &g...

...e. The issue I would like to address is which transformations > should > >>> we allow as safe transformations and how should we update the internal > path > >>> profile data structures if we allow this at all. > >>> > >>> > > + Verify with PGOEdge info ? > >>> > >>> > Ditto. > >>> > >>> Verification with PGOEdge info implies that the edge frequencies > derived > >>> from path profiles and via instrprof should be equal. > >>> > >>> > > + Handle se...

...idates the >>> profile. The issue I would like to address is which transformations should >>> we allow as safe transformations and how should we update the internal path >>> profile data structures if we allow this at all. >>> >>> > > + Verify with PGOEdge info ? >>> >>> > Ditto. >>> >>> Verification with PGOEdge info implies that the edge frequencies derived >>> from path profiles and via instrprof should be equal. >>> >>> > > + Handle setjmp, longjmp, early program termination...

...vm/Analysis gets PathEncoding, PathDecoding and PathProfileInfo module passes + llvm/Transforms/Instrumentation gets PathProfileInstrumentation module pass + PathProfileInfo offers const only public methods to query info Open Issues : + Update PathProfileInfo on CFG transformations ? + Verify with PGOEdge info ? + Handle setjmp, longjmp, early program termination, noreturn calls Please let me know your comments on this proposal as a GSoC project. Any comments on how to refine this proposal are welcome. I can also elaborate on specific details of our implementation if there is interest on the mail...

...sformations >> >>> should >> >>> we allow as safe transformations and how should we update the internal >> >>> path >> >>> profile data structures if we allow this at all. >> >>> >> >>> > > + Verify with PGOEdge info ? >> >>> >> >>> > Ditto. >> >>> >> >>> Verification with PGOEdge info implies that the edge frequencies >> >>> derived >> >>> from path profiles and via instrprof should be equal. >> >>&gt...