similar to: Testing LLVM XRay

Eric: thanks for bringing this to my attention; I somehow missed this email. Hi Buddhika, Thanks for getting in touch and for your interest. Please submit an application whenever the registration period opens and let me/us know if you have any question regarding the project and/or GSoC. Regards, Nuno On Sun, Feb 25, 2018 at 1:37 PM buddhika chamith via llvm-dev <llvm-dev at

Hi Devs, I am a PhD student at Indiana University. I am interested in working on the project on function attribute inference. My current research direction involves runtime binary optimization using JIT compilation from a lifted LLVM IR. I am hoping various runtime information coupled with static analysis on the IR can provide better avenues for runtime code JITTIng (akin to PGO). Anyway I think

On Sun, Feb 25, 2018 at 1:37 PM buddhika chamith via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hi Devs, > > I am a PhD student at Indiana University. I am interested in working on > the project on function attribute inference. My current research direction > involves runtime binary optimization using JIT compilation from a lifted > LLVM IR. I am hoping various

Hi all, I want to test X-ray performance and compare it with other research tools, so I use Clang 7.0.0 to compile and instrument GNU binutils-2.3.1 with the following commands: cd binutils-2.31/ mkdir build cd build/ CC=$local/clang CXX=$local/clang++ CFLAGS=-fxray-instrument CXXFLAGS=-fxray-instrument ../configure --prefix=/home/zhangysh1995/local make Then I extract instrumentation map

Hi Nuno, Thanks. Appreciate if I can get some specific pointers to related code or documentation that I could start looking to to get myself oriented. I just started looking to in to lib/Analysis a bit. Regards Buddhika On Thu, Mar 1, 2018 at 4:50 AM, Nuno Lopes <nunoplopes at sapo.pt> wrote: > Eric: thanks for bringing this to my attention; I somehow missed this > email. >

Hi All, I have shared the draft now. Please check and comment if you get time. Regards Buddhika On Sat, Mar 17, 2018 at 4:29 PM, buddhika chamith <chamibuddhika at gmail.com> wrote: > Hi All, > > I have attached a draft (somewhat incomplete yet) of my proposal herewith. > Greatly appreciate any feed back on it (specially on the timeline bit since > I am not yet quite sure

Hi all, I am trying to add XRay support to the IR produced by GHC. Getting the basics working is not too complicated after adding the right function attribute but any analysis shows the function names but not the locations of the functions. In particular, I run a program which has been instrumented as follows: XRAY_OPTIONS="patch_premain=true xray_mode=xray-basic verbosity=1" ./llvm

Hi there, I have a problem using the function call tracing tools that is designed in llvm tools set. My aim is to record every function call that a program makes when it run. However, for whatever reason, a simple matrix multiply c program that I wrote cannot record all the function calls that happened when the program run. Here is the program: matrix.c #include <stdio.h> void

Definitely have a look at the current analyses: - llvm/Transforms/IPO/FunctionAttrs.cpp - llvm/Transforms/IPO/InferFunctionAttrs.cpp Also, study the semantics of these attributes, starting with the docs: http://llvm.org/docs/LangRef.html#function-attributes Also, grep the LLVM sources for test cases that use the attributes to see examples on how they are used for optimization. Finally, have a

> On 3 Dec 2018, at 23:01, Matthew Pickering via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Is anyone able to help me with this or suggest where I might be able > to get help? You’ve asked the right place, apologies for the delay I’m supposed to be answering these questions. > > Matt > On Mon, Nov 26, 2018 at 3:02 PM Matthew Pickering > <matthewtpickering

Hi David, Sorry for taking a few days to reply. It's not easy for you to compile a Haskell file to see the problem as the debug information is still WIP. Below I prove the IR for a simple hello world program which you can feed into llc. https://gist.github.com/05296933e37e87533a51d493b46aa48d The `out.ir` file can be passed straight to `llc`. Can you see anything obviously wrong? Matt

I am trying to parse LLVM IR from a bit code file. I went through the following steps. hello.cpp #include <iostream> int main() { std::cout << "Hello world!" << "\n"; return 0;} dump.cpp #include <llvm/IR/Module.h>#include <llvm/IRReader/IRReader.h>#include <llvm/IR/LLVMContext.h>#include <llvm/Support/SourceMgr.h> using

Hello, I am initializing FDR mode and finalizing/flushing the buffers manually. XRay does not log calls from the main thread unless there is a function call after __xray_log_finalize(). This behavior is abnormal since one would expect the trace file to contain all function calls made up to the point when __xray_log_finalize() is called. To demonstrate this behavior, I have taken the test case

hi all, I am using Ubuntu 7.04 version. please can anyone tell me what are the files that copy in to a computer when it install. the following are the some of observations i got. After installing the theora it will copy the required files to the following places (default) according to the configure script. libtheora: ................... /usr/local/lib C header files: ..............

My back-end code generator uses LLVM 5.0.1 to optimize and generate code for x86_64. If I run it on a given sample of IR, it takes almost 5 minutes to generate object code. 95%+ of this time is spent in MergeConsecutiveStores(). (One function has a basic block with 14000 instructions, which is a pathological case for MergeConsecutiveStores.) If, instead, I dump out the LLVM IR, and manually

> On 29 May 2018, at 22:02, David Jones via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > My back-end code generator uses LLVM 5.0.1 to optimize and generate code for x86_64. > > If I run it on a given sample of IR, it takes almost 5 minutes to generate object code. 95%+ of this time is spent in MergeConsecutiveStores(). (One function has a basic block with 14000

> On Apr 6, 2017, at 2:52 AM, Renato Golin <renato.golin at linaro.org> wrote: > > On 6 April 2017 at 05:49, Dean Michael Berris <dean.berris at gmail.com> wrote: >> I'll have a look if I can untangle that. >> >> Thanks Renato! > > Well, that didn't last long. Now I remember why last time I fixed > hundreds of warnings on the docs directly

# Objective Implement an XRay mode 'xray-profiling' that gathers stack trace latencies/durations and builds histograms to provide basic statistics about where time is going in an execution of the application. # Background XRay has two modes currently implemented in compiler-rt: a basic (nee naive) mode and flight data recorder (FDR) mode. Basic mode logging, when enabled, will collect

Hi everyone, TL;DR: With current pending patches applied in compiler-rt and llvm, and trunk clang, you can build your application with XRay tracing enabled on Linux with tracing enabled before main starts, and logging stops when the main thread exits. Just a quick update, I have some patches under review that when applied cleanly to LLVM and compiler-rt allows for building applications with XRay

FYI: Patch is now available for review in https://reviews.llvm.org/D44620. On Thu, Feb 15, 2018 at 1:34 PM Dean Michael Berris <dean.berris at gmail.com> wrote: > # Objective > > Implement an XRay mode 'xray-profiling' that gathers stack trace > latencies/durations and builds histograms to provide basic statistics about > where time is going in an execution of the