search for: 75625

...se differences on some real example? I'd like to keep everything >> working at least as good as it was before (modulo some other features, >> like function counts or basic block traces, which we don't really >> support). > > I have to compare the revisions 75622 and 75625 to check what's going on > there, but maybe its also due to undeleted llvmprof.out files? I have compared the revisions now and apart from the passes being executed faster (according to -time-passes) there is no difference in the llvm-prof output. Andi

..."" "" "" [41] "900" "" "" "" "1000" > > y <- x * x > y [1] 10000 5625 2500 625 0 625 2500 5625 10000 [10] 15625 22500 30625 40000 50625 62500 75625 90000 105625 [19] 122500 140625 160000 180625 202500 225625 250000 275625 302500 [28] 330625 360000 390625 422500 455625 490000 525625 562500 600625 [37] 640000 680625 722500 765625 810000 855625 902500 950625 1000000 > > plot(x, y, xlab=xtickLabels) > Thanks...

...nces on some real example? I'd like to keep everything >>> working at least as good as it was before (modulo some other features, >>> like function counts or basic block traces, which we don't really >>> support). >> I have to compare the revisions 75622 and 75625 to check what's going on >> there, but maybe its also due to undeleted llvmprof.out files? > I have compared the revisions now and apart from the passes being > executed faster (according to -time-passes) there is no difference in > the llvm-prof output. > > Andi -- This...

...igate both of > these differences on some real example? I'd like to keep everything > working at least as good as it was before (modulo some other features, > like function counts or basic block traces, which we don't really > support). I have to compare the revisions 75622 and 75625 to check what's going on there, but maybe its also due to undeleted llvmprof.out files? > [...] >> Index: include/llvm/Analysis/Passes.h >> =================================================================== >> --- include/llvm/Analysis/Passes.h (revision 74697) >> +...

Hi Andreas, Thanks for breaking things up. I applied two pieces of this patch in separate no-functionality-change commits, here: http://llvm.org/viewvc/llvm-project?view=rev&revision=75623 and here: http://llvm.org/viewvc/llvm-project?view=rev&revision=75625 I merged in my changes to your patch, which results in the attached patch. There may be some missed merge errors. The main problem I have with the rest of this patch is that it causes a regression in llvm-prof's behavior. I tried running edge profiling on the MultiSource/Applications/aha bench...

Hi, this is the first in a series of patches to cleanup and improve the LLVM Profiling Infrastructure. First and foremost this patch removes duplicate functionality from ProfileInfoLoader and ProfileInfo: The ProfileInfoLoader performed not only the loading of the profile information but also some synthesis of block and function execution counts from edge profiling information. Since the

Hi, I''ve tried to reproduce the example from section 4.1 (simple source policy routing) but without success. The setup is the same as in the example, with only two differences: there is additionally a gre tunnel which doesn''t seem to disturb here, and one interface does not masquerade at all, as it''s thought to be used from the router only. Besides that, and the

Hi Daniel, Daniel Dunbar wrote: > Hi Andreas, > > First, thanks again for undertaking this work and submitting it back. There is a > lot of good stuff here and it would be great to see it get back into the tree. Thanks for taking the time to review this, I know its a huge patch. I still have a few questions on how you would like this patch to be re-factored and split up. > [...]