similar to: [LLVMdev] unable to decode llvmpro.out for path profiling

Hi, I am a student at IIT Kanpur. I am working on Path Profiling, i just came with a need to know about the number of static paths in a program(actually in a function) before it's actually get run. As i saw in PathProfiling.c file in llvm\runtime\libprofile they are just storing the path information at run time and dynamically adding entries for the new path. But i need to know the number of

On the off chance anyone here is interested in more performance results, I compiled and ran the fastest of the implementations of the ray tracer in C++ from my language comparison: http://www.ffconsultancy.com/languages/ray_tracer/ This is a small program with a relatively large hotpath. Specifically, around 30% of the time is spend in the ray sphere intersection but another 30% is also

Hi, I am a student at IIT Kanpur. I am working on Path Profiling, i just came with a need to know about the number of static paths in a program(actually in a function) before it's actually get run. As i saw in PathProfiling.c file in llvm\runtime\libprofile they are just storing the path information at run time and dynamically adding entries for the new path. But i need to know the number of

The following series makes use of the skb fragment API (which is in 3.2 +) to add a per-paged-fragment destructor callback. This can be used by creators of skbs who are interested in the lifecycle of the pages included in that skb after they have handed it off to the network stack. The mail at [0] contains some more background and rationale but basically the completed series will allow entities

Hi, Can someone tell me what was Gaurav Arora's exact contribution in the Clustering Search Results part during GSoC 2014? I guess that will be more helpful in understanding his code. Regards Karthik On Tue, Dec 16, 2014 at 4:06 AM, Olly Betts <olly at survex.com> wrote: > On Mon, Dec 15, 2014 at 06:56:39PM +0530, karthik iyer wrote: >> Could some one tell me some specific

I mis-spoke. It seems I had two collections of functions in the same directory. One by Colin Goodall, and one by David Scott (I have no record of where he is/was located). It is the *latter* collection that does all its work from within Fortran. I'll have another look at what Colin Goodall actually wrote to see if it could be useful to guarav. cheers, Rolf Turner rolf at

Hello, This is a problem for which there seem to be several solutions online, but not really. My question was about plotting a curve over the histogram. All the previous posts and messages talk about generating a *density histogram*using (freq=F) and then plotting the density curve. However, I find that that seriously distorts my data and the plot becomes confounding to the viewer. I was

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. > [...]

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. I have a few major high-level comments on the patch. First off, the patch is quite large and should be broken down into separate incremental changes which are easier to review and apply. I think the patches should more or less

Hi all, as proposed in http://lists.cs.uiuc.edu/pipermail/llvmdev/2009-February/020396.html I implemented the algorithm presented in [Ball94]. It only instruments the minimal number of edges necessary for edge profiling. The main changes introduced by this patch are: *) a interface compatible rewrite of ProfileInfo *) a cleanup of ProfileInfoLoader (some functionality in ProfileInfoLoader

Initially out there as #965245. I strongly prefer to build ARM64 packages on non-ARM systems. Something about my main build machine having twice the cores and twice the clock speed. As such after many builds I've managed to generate a set of patches which appear to mostly function to get functioning cross-builds of Xen. These are NOT a 100% solution. Some packaging hacks were needed. In

xen/arch/x86/crash.c | 116 ++++++++++++++++++++++++++++++++++----- xen/arch/x86/machine_kexec.c | 19 ++++++ xen/arch/x86/x86_64/entry.S | 34 +++++++++++ xen/include/asm-x86/desc.h | 45 +++++++++++++++ xen/include/asm-x86/processor.h | 4 + 5 files changed, 203 insertions(+), 15 deletions(-) Experimentally, certain crash kernels will triple fault very early