search for: priyendra

...arning curve. I notice that the configure script has a --with-oprofile option. In addition to enabling that, is there something else that also needs to be done? My copy of LLVM is compiled with --enable-optimized. Will --with-oprofile work fine with that or should I disable optimized? Regards, -- Priyendra On Mon, Mar 4, 2013 at 11:54 AM, Kaylor, Andrew <andrew.kaylor at intel.com>wrote: > Hi Priyendra,**** > > ** ** > > There is support for oprofile and Intel® VTune™ Performance Analyzer, but > either one needs to be explicitly turned on during the build process. If >...

...o profiling the generated code? My project uses gperftools pprof for profiling etc. Is there a way to hook the two up? Are there any other profiling method that works? This page describes how to debug JIT code with GDB. I wonder if something similar could be done for gperftools/pprof? Regards, -- Priyendra -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130303/495823af/attachment.html>

Hi Priyendra, There is support for oprofile and Intel(r) VTune(tm) Performance Analyzer, but either one needs to be explicitly turned on during the build process. If you use MCJIT (as opposed to the older JIT) then oprofile support isn't in place yet. Both of these work by providing a JITEventListener th...

...production. Using the existing gdb/JIT interface support is > probably far too heavyweight for production. If you roll your own, you can > record the PC ranges efficiently and that should be good enough to capture > traces from production. > > > On Tue, Nov 12, 2013 at 2:56 PM, Priyendra Deshwal < > deshwal at thoughtspot.com> wrote: > >> [Resending this email after subscribing to the group. Got an error >> message the previous time around] >> >> Hey guys, >> >> In our project we have the following workflow: >> >> - Given...

...handler that does stack unwinding and symbolization upon crash. Based on my reading so far, we need to implement a JITEventListener which would keep track of the dynamically generated symbol addresses and use the resulting maps for symbolization. Will that work? Is there a simpler way? Thanks, -- Priyendra -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20131112/e6677a44/attachment.html>

...t way to capture traces from production. Using the existing gdb/JIT interface support is probably far too heavyweight for production. If you roll your own, you can record the PC ranges efficiently and that should be good enough to capture traces from production. On Tue, Nov 12, 2013 at 2:56 PM, Priyendra Deshwal <deshwal at thoughtspot.com>wrote: > [Resending this email after subscribing to the group. Got an error message > the previous time around] > > Hey guys, > > In our project we have the following workflow: > > - Given a user request, we construct a C++ program...

...uction. Using the existing gdb/JIT interface support is > probably far too heavyweight for production. If you roll your own, you can > record the PC ranges efficiently and that should be good enough to capture > traces from production. > > > > On Tue, Nov 12, 2013 at 2:56 PM, Priyendra Deshwal < > deshwal at thoughtspot.com> wrote: > > [Resending this email after subscribing to the group. Got an error > message the previous time around] > > > > Hey guys, > > > > In our project we have the following workflow: > > > > - Given...

...st way to capture traces from production. Using the existing gdb/JIT interface support is probably far too heavyweight for production. If you roll your own, you can record the PC ranges efficiently and that should be good enough to capture traces from production. On Tue, Nov 12, 2013 at 2:56 PM, Priyendra Deshwal <deshwal at thoughtspot.com<mailto:deshwal at thoughtspot.com>> wrote: [Resending this email after subscribing to the group. Got an error message the previous time around] Hey guys, In our project we have the following workflow: - Given a user request, we construct a C++ prog...

...st way to capture traces from production. Using the existing gdb/JIT interface support is probably far too heavyweight for production. If you roll your own, you can record the PC ranges efficiently and that should be good enough to capture traces from production. On Tue, Nov 12, 2013 at 2:56 PM, Priyendra Deshwal <deshwal at thoughtspot.com<mailto:deshwal at thoughtspot.com>> wrote: [Resending this email after subscribing to the group. Got an error message the previous time around] Hey guys, In our project we have the following workflow: - Given a user request, we construct a C++ prog...

...traces from production. Using the existing gdb/JIT interface support is > probably far too heavyweight for production. If you roll your own, you can > record the PC ranges efficiently and that should be good enough to capture > traces from production. * On Tue, Nov 12, 2013 at 2:56 PM, Priyendra Deshwal <deshwal at thoughtspot.com <http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev>>wrote: >* [Resending this email after subscribing to the group. Got an error message *>* the previous time around] *>>* Hey guys, *>>* In our project we have the following wo...

...handler that does stack unwinding and symbolization upon crash. Based on my reading so far, we need to implement a JITEventListener which would keep track of the dynamically generated symbol addresses and use the resulting maps for symbolization. Will that work? Is there a simpler way? Thanks, -- Priyendra -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20131112/e25e7591/attachment.html>

Hi, I would like to start a discussion about enabling the loop vectorizer by default for -Os. The loop vectorizer can accelerate many workloads and enabling it for -Os and -O2 has obvious performance benefits. At the same time the loop vectorizer can increase the code size because of two reasons. First, to vectorize some loops we have to keep the original loop around in order to handle the last