search for: branchfrequencyinfo

...a module level, but once > this has been done it can be accessed at any level (including function). > > In LLVM 3.1 ProfileInfo stores block execution frequencies (use > -profile-loader). > > For LLVM svn you can look at BlockFrequencyInfo, which I generates its > data from BranchFrequencyInfo, which in turn uses the branch weight > metadata (set by -profile-metadata-loader). I haven't actually tried > this though, so I'm not sure how accurately the block frequencies are > maintained. > > >> Also, I was able to produce a 'llvmprof.out' file. What...

...data really needs to be loaded at a module level, but once this has been done it can be accessed at any level (including function). In LLVM 3.1 ProfileInfo stores block execution frequencies (use -profile-loader). For LLVM svn you can look at BlockFrequencyInfo, which I generates its data from BranchFrequencyInfo, which in turn uses the branch weight metadata (set by -profile-metadata-loader). I haven't actually tried this though, so I'm not sure how accurately the block frequencies are maintained. > Also, I was able to produce a 'llvmprof.out' file. What is the format of > this...

Thanks Alastair. Is it possible to associate the branch frequency counts with the basic blocks in the intermediate representation? (e.g. Can I access basic block frequencies in runOnFunction()?) Also, I was able to produce a 'llvmprof.out' file. What is the format of this file? How can I parse it? Thanks. -Apala > > > On 09/07/2012 01:25 PM, Alastair Murray wrote: >

...>> this has been done it can be accessed at any level (including function). >> >> In LLVM 3.1 ProfileInfo stores block execution frequencies (use >> -profile-loader). >> >> For LLVM svn you can look at BlockFrequencyInfo, which I generates its >> data from BranchFrequencyInfo, which in turn uses the branch weight >> metadata (set by -profile-metadata-loader). I haven't actually tried >> this though, so I'm not sure how accurately the block frequencies are >> maintained. >> >> >>> Also, I was able to produce a 'llvmprof...

...accessed at any level (including >>> function). >>> >>> In LLVM 3.1 ProfileInfo stores block execution frequencies (use >>> -profile-loader). >>> >>> For LLVM svn you can look at BlockFrequencyInfo, which I generates its >>> data from BranchFrequencyInfo, which in turn uses the branch weight >>> metadata (set by -profile-metadata-loader). I haven't actually tried >>> this though, so I'm not sure how accurately the block frequencies are >>> maintained. >>> >>> >>>> Also, I was able to...

...>> this has been done it can be accessed at any level (including function). >> >> In LLVM 3.1 ProfileInfo stores block execution frequencies (use >> -profile-loader). >> >> For LLVM svn you can look at BlockFrequencyInfo, which I generates its >> data from BranchFrequencyInfo, which in turn uses the branch weight >> metadata (set by -profile-metadata-loader). I haven't actually tried >> this though, so I'm not sure how accurately the block frequencies are >> maintained. >> >> >>> Also, I was able to produce a 'llvmprof...

...uding >>>> function). >>>> >>>> In LLVM 3.1 ProfileInfo stores block execution frequencies (use >>>> -profile-loader). >>>> >>>> For LLVM svn you can look at BlockFrequencyInfo, which I generates its >>>> data from BranchFrequencyInfo, which in turn uses the branch weight >>>> metadata (set by -profile-metadata-loader). I haven't actually tried >>>> this though, so I'm not sure how accurately the block frequencies are >>>> maintained. >>>> >>>> >>>>...

Michael Spencer via llvm-dev <llvm-dev at lists.llvm.org> writes: > I've recently implemented profile guided section layout in llvm + lld using > the Call-Chain Clustering (C³) heuristic from > https://research.fb.com/wp-content/uploads/2017/01/cgo2017-hfsort-final1.pdf > . In the programs I've tested it on I've gotten from 0% to 5% performance > improvement over

I've recently implemented profile guided section layout in llvm + lld using the Call-Chain Clustering (C³) heuristic from https://research.fb.com/wp-content/uploads/2017/01/cgo2017-hfsort-final1.pdf . In the programs I've tested it on I've gotten from 0% to 5% performance improvement over standard PGO with zero cases of slowdowns and up to 15% reduction in ITLB misses. There are