search for: bpi

...mBranch uses BranchProbabilityInfo to decide whether its worth trying the InductiveRangeCheckElimination transformation. For the following example: void split() { for (int i = 0; i < 100; ++i) { if (i < 99) do_something() else do_something_else() } } But the reported BPI is reported as 50/50 to whether do_something will be called, but we can see with our human eyes that this should be 99%. So two questions: - why is BPI used to enable the transformation? - would it not be more useful for BPI to use something like inductive range analyis to calculate the probabilit...

...ting hard dependency of IRCE on BranchProbability analysis. If I understand it right, in a new pass manager there are only two ways for loop analysis to ask for the result of an "outer" (function/module-level) analysis:   - get it from a predefined LoopStandardAnalysisResults set     BPI is not there, so it unsuitable for me right now   - query a cached result via getCachedResult of an outer analysis manager proxy     only works if somebody already scheduled the analysis I followed the cached-result way and that essentially means that for every presence of 'irce' in a...

...mBranch uses BranchProbabilityInfo to decide whether its worth trying the InductiveRangeCheckElimination transformation. For the following example: void split() { for (int i = 0; i < 100; ++i) { if (i < 99) do_something() else do_something_else() } } But the reported BPI is reported as 50/50 to whether do_something will be called, but we can see with our human eyes that this should be 99%. So two questions: - why is BPI used to enable the transformation? - would it not be more useful for BPI to use something like inductive range analyis to calculate the probabilit...

Am 13.06.2020 um 13:47 schrieb Michael Keuter: Hi > Try "sip show peer <peername>" for a phone. So: mobile phone: bpi*CLI> sip show peer 0049177xxxxxxx * Name : 0049177xxxxxxx Description : Secret : <Set> MD5Secret : <Not set> Remote Secret: <Not set> Context : default Record On feature : automon Record Off feature : automon Subscr.Con...

...size incorrectly. So you are able to ping with > size 1464 and not with 1466. How about trying same ping sizes from the > internet towards your site? I mean trying to ping from sites with > higher MTU than yours without lower MTU links in the path. lucabert at ns:~$ ping -4 -M do -s 1465 bpi.d.lucabert.com PING bpi.d.lucabert.com (93.241.91.232) 1465(1493) bytes of data. From 62.156.246.57 (62.156.246.57) icmp_seq=1 Frag needed and DF set (mtu = 1492) ping: local error: Message too long, mtu=1492 ping: local error: Message too long, mtu=1492 ping: local error: Message too long, mtu=1...

...ant. I think > my email got lost that time, in the sea of emails we see on the dev mail > list. profile.pl has seen a non-cleanup related commit in 5 years ... It seems so simple I'm not sure I see a need for it. But clearly you use it! > I must confess that I was not aware of the BPI and BFI infrastructures. > The breaking of the profiling infrastructure always baffled me. Now it > makes sense, since it has been superseded by these new frameworks. > > Anyway, if you guys decide to keep the old profiling framework, it would > be good. As Alastair has mentioned, th...

...used Alaw as Codec. > Am 13.06.2020 um 17:23 schrieb Luca Bertoncello <lucabert at lucabert.de>: > > Am 13.06.2020 um 13:47 schrieb Michael Keuter: > > Hi > >> Try "sip show peer <peername>" for a phone. > > So: > > mobile phone: > bpi*CLI> sip show peer 0049177xxxxxxx > > > > > * Name : 0049177xxxxxxx > > > Description : > > > Secret : <Set> > > > MD5Secret : <Not set> > > > Remote Secret: <Not set> > > > Context...

Am 13.06.2020 09:30, schrieb Luca Bertoncello: Hi again (again) I noticed right now another strange detail... I made a call using my mobile phone (connected to the Asterisk). The quality was top... Maybe is the problem in a codec used from our phones at homes? Could someone suggest me how to check the codec used by my mobile phone and the codec used by the phones at home? Thanks Luca

...ith dependency of loop passes on >> BranchProbabilityInfo. >> (some loop passes, like IRCE can use it for profitability analysis). >> > The only solution that appears to be reasonable there is to teach all the >> loops passes that need to be pipelined >> to preserve BPI (or any other module/function-level analyses) similar to >> how they preserve DominatorTree and >> other "LoopStandard" analyses. >> > > Is this implemented - do the loop passes preserve BPI? > > Nope, not implemented right now. > One of the problems is th...

...n tiny one line fixes to keep them working. I offered to send these small patches to keep these scripts working, to the LLVM dev so that others can use it if they want. I think my email got lost that time, in the sea of emails we see on the dev mail list. I must confess that I was not aware of the BPI and BFI infrastructures. The breaking of the profiling infrastructure always baffled me. Now it makes sense, since it has been superseded by these new frameworks. Anyway, if you guys decide to keep the old profiling framework, it would be good. As Alastair has mentioned, the llvm-prof helps in a w...

...(some loop passes, like IRCE can use it for profitability >> analysis). >> >> The only solution that appears to be reasonable there is >> to teach all the loops passes that need to be pipelined >> to preserve BPI (or any other module/function-level >> analyses) similar to how they preserve DominatorTree and >> other "LoopStandard" analyses. >> >> >> Is this implemented - do the loop passes preserve BPI? > Nope, not implemente...

Hello Alastair, Yeah like I said, I was not aware of the new profile framework being developed. Interestingly BPI and BFI didnt turn up in any searches either. Anyway, I will take a look at them and see how they differ from the existing tools. Profile.pl is understandably a very simple script, but it does make it easier to see some preliminary profile results and identity the hot portions of a program which...

...I between the loop passes. We detect > PGO based on whether PSI has profile summary info. (For the old pass > manager, implement a similar approach by using LazyBlockFrequencyInfo.) There is already an optional analysis in LoopStandardAnalysisResults - MemorySSA. We can do the same for BFI/BPI. And, yes - preserving those through loop passes is a cornerstone to this approach. > > - Add a new proxy ModuleAnalysisManagerLoopProxy for a loop pass to be > able to get to the ModuleAnalysisManager in one step and PSI through it. This is just an optimization of compile-time, saves on...

...issue somewhat recently with dependency of loop passes on > BranchProbabilityInfo. > (some loop passes, like IRCE can use it for profitability analysis). > The only solution that appears to be reasonable there is to teach all the > loops passes that need to be pipelined > to preserve BPI (or any other module/function-level analyses) similar to > how they preserve DominatorTree and > other "LoopStandard" analyses. > Is this implemented - do the loop passes preserve BPI? In buildFunctionSimplificationPipeline (where LoopFullUnrollPass is added as in the sketch),...

...you were actively working on the existing ProfileInfo and profile loading infrastructure we would have jumped in quickly to redirect things. I'll provide a bit of feedback below, but we should really hold the main part of this discussion on a separate thread, as ultimately *how* you can use the BPI and BFI analyses and the metadata they are predicated on is independent from whether we remove the existing code... The important thing is that you can use them, and that the existing code won't help much (if at all). I would like to continue working on profiling support but I'm not > a...

...t at profile information from general >> analyses and transforms: a dedicated analysis pass that manages access to >> the profile info. >> > > > This is not the case as of today. > Again, my whole comment was that these are no longer being correctly followed. > BPI is a dedicated analysis pass to manage branch probability profile > information, but this pass is only used in limited situations (e.g, for > BFI, profile update in jump-threading etc) -- using it it requires more > memory as well as incremental update interfaces. Many transformation >...

...hofer at apple.com> wrote: > The LoopVectorizer depends on LCSSA and LoopSimplify. Both are loop > passes. We will have to make them also available as utility functions. Yuck. We still need to fix these at least, but that's much better than teaching *all* the loop passes to preserve BPI and BFI. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20140121/a2943357/attachment.html>

...you are able to ping with >> size 1464 and not with 1466. How about trying same ping sizes from the >> internet towards your site? I mean trying to ping from sites with >> higher MTU than yours without lower MTU links in the path. > > lucabert at ns:~$ ping -4 -M do -s 1465 bpi.d.lucabert.com > PING bpi.d.lucabert.com (93.241.91.232) 1465(1493) bytes of data. > From 62.156.246.57 (62.156.246.57) icmp_seq=1 Frag needed and DF set > (mtu = 1492) > ping: local error: Message too long, mtu=1492 > ping: local error: Message too long, mtu=1492 > ping: local e...

...not polynomials anymore, so the name is not really appropriate). After studying R calls, expressions and functions a bit more, I gave myself the homework of producing an animation out of my recent toy. The resulting animation, and also the sources, are available at: http://pinard.progiciels-bpi.ca/plaisirs/nr-anim-01.html P.S. - My intent was studying R, much more than producing art :-). I'm sure anyone could do nicer, playing a few hours with this! -- Fran?ois Pinard http://pinard.progiciels-bpi.ca

...nalysis). >>>> >>>> The only solution that appears to be reasonable >>>> there is to teach all the loops passes that >>>> need to be pipelined >>>> to preserve BPI (or any other >>>> module/function-level analyses) similar to how >>>> they preserve DominatorTree and >>>> other "LoopStandard" analyses. >>>> >>>> >>>>...