search for: xray

...uild the toolchain in one build directory, including `compiler-rt`. 2) Build the toolchain again with the just built toolchain in step 1, but this time with `-DLLVM_USE_SANITIZER=MemoryWithOrigins`. I get some msan errors, but of this kind instead of the one I'm expecting: ==== $ ./unittests/XRay/XRayTests ==236769==WARNING: MemorySanitizer: use-of-uninitialized-value #0 0x70eef8 (/usr/local/google/home/dberris/xray/llvm-project-build-msan/unittests/XRay/XRayTests+0x70eef8) #1 0x70d2dc (/usr/local/google/home/dberris/xray/llvm-project-build-msan/unittests/XRay/XRayTests+0x70d2dc)...

...> 2) Build the toolchain again with the just built toolchain in step 1, > > but this time with `-DLLVM_USE_SANITIZER=MemoryWithOrigins`. > > > > I get some msan errors, but of this kind instead of the one I'm > expecting: > > > > ==== > > $ ./unittests/XRay/XRayTests > > ==236769==WARNING: MemorySanitizer: use-of-uninitialized-value > > #0 0x70eef8 > > > (/usr/local/google/home/dberris/xray/llvm-project-build-msan/unittests/XRay/XRayTests+0x70eef8) > > #1 0x70d2dc > > > (/usr/local/google/home/dberris/xray/l...

...gain with the just built toolchain in step 1, > > > but this time with `-DLLVM_USE_SANITIZER=MemoryWithOrigins`. > > > > > > I get some msan errors, but of this kind instead of the one I'm > expecting: > > > > > > ==== > > > $ ./unittests/XRay/XRayTests > > > ==236769==WARNING: MemorySanitizer: use-of-uninitialized-value > > > #0 0x70eef8 > > > > (/usr/local/google/home/dberris/xray/llvm-project-build-msan/unittests/XRay/XRayTests+0x70eef8) > > > #1 0x70d2dc > > > > (/usr/local/g...

...hrough the code and it looks like we're always just > using the function id when we should be using the symbol name. Let me > land a patch to fix this. Thanks Dean. > Is there a way to find the function name from the identifier? > > You can try this manually by using the `llvm-xray extract -symbolize` > tool to get a YAML file that maps the function id's to symbols, but > that's a roundabout way of doing it. Ideally the graph-diff tool > should just do it. > > I have tried this strangely I got this error $> llvm-xray extract -symbolize xray-log.clan...

# 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...

Hi, The call graphs generated by "*llvm-xray graph*" has function names, while the "*llvm-xray graph-diff*" doesn't shows function names. This is the command I am using llvm-xray graph-diff xray-log.clang.1 xray-log.clang.2 -instr-map=../xray-build/bin/clang -o diff.dot Attached is the portion of the generated diff graph...

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 application. > > # Background > > XRay has two modes currently implemented in compiler-rt: a basic (nee...

Hi llvm-dev, I've been implementing a tool for analysing XRay traces. A recap of XRay's original RFC [0] mentions a tool that does function call accounting as a starting point. This is implemented currently in D21987 [1], and is being reviewed by David Blaikie. One key issue in that review is the dependency between the log format determined by the XRay r...

Hi Dean, I haven't looked very closely at XRay so far, but I'm wondering if making CTF (common trace format, e.g. see http://diamon.org/ctf/) the default format for XRay traces would be useful? It seems it'd be nice to be able to reuse some of the tools that already exist for CTF, such as a graphical viewer (http://tracecompass.org/) or...

...e same binary? > > If that doesn't work then it sounds like a bug. > > Cheers > > On Mon, Jan 7, 2019 at 7:32 PM Dangeti Tharun kumar via llvm-dev > <llvm-dev at lists.llvm.org> wrote: > > > > Hi, > > > > The call graphs generated by "llvm-xray graph" has function names, while > the "llvm-xray graph-diff" doesn't shows function names. > > This is the command I am using > > > > llvm-xray graph-diff xray-log.clang.1 xray-log.clang.2 > -instr-map=../xray-build/bin/clang -o diff.dot > > > &...

Hi all, I was interested in trying out the Xray profiling component in LLVM and was trying to compile a C program with Clang with Xray flags. Unfortunately, I keep getting a linker error everytime I try to compile the C program with Clang. However, the error goes away when I try to compile the same C program with Clang++ with -xc++ flag. Search...

On Fri, Jun 17, 2016 at 5:42 AM Matthias Braun via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Some of this overlaps with the features in XRay ( > http://lists.llvm.org/pipermail/llvm-dev/2016-April/098901.html). > > Matthias beat me to it! >From reading the RFC, it seems that some of what XRay is doing on the instrumentation side is very similar to what CSI enables. The current implementation I'm working with (in http://...

I'm wondering why the lit tests didn't catch this as part of testing rc1 on ARM. On Thu, Jan 26, 2017 at 11:25 AM, Serge Rogatch <serge.rogatch at gmail.com> wrote: > XRay is tested automatically on build-bots with tests in LLVM and > compiler-rt . Or are you asking for manual testing instructions? > Of these 2 patches, the compiler-rt patch depends on LLVM patch because the > tests compiler-rt\test\xray\TestCases\Linux would fail without the fix in > LLV...

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=&quo...

Hi Dean/Serge, I just spotted this on our bots: First failure, unrelated commit: http://lab.llvm.org:8011/builders/clang-cmake-armv7-a15-full/builds/3190 'XRay-Unit :: unit/XRayFDRLoggingTest/FDRLoggingTest.Simple' FAILED llvm/projects/compiler-rt/lib/xray/tests/unit/fdr_logging_test.cc:55: Failure Expected: FDRLogging_init(kBufferSize, kBufferMax, &Options, sizeof(FDRLoggingOptions)) Which is: 0 To be equal to: XRayLogInitStatus::XRAY...

How is XRay tested? IIRC, Renato didn't see any test failures on ARM? Merging sounds reasonbaly, I'd just like to understand what's the risk for the branch. On Thu, Jan 26, 2017 at 10:29 AM, Serge Rogatch <serge.rogatch at gmail.com> wrote: > Hans, these changes reached trunk in https://...

...;brian.cain at gmail.com> wrote: > > > >> On Tue, Dec 5, 2017 at 9:49 AM, Dean Michael Berris via cfe-dev <cfe-dev at lists.llvm.org> wrote: >> Hi cfe-dev@ and llvm-dev@, >> >> I've attached a Chrome trace-viewer readable trace of a clang built with XRay instrumentation (additional build/link flags="-fxray-instrument -fxray-instruction-threshold=75") with the latest "top-of-trunk" version of clang with the recent updates to the XRay runtime supporting record filtering. >> >> To load the attached file, go to 'chr...

On Wed, Nov 22, 2017 at 10:37 AM, Dean Michael Berris <dean.berris at gmail.com> wrote: > > On 22 Nov 2017, at 02:32, comic fans <comicfans44 at gmail.com> wrote: > > with some dirty hack , I've made xray runtime 'built' on windows , > > > \o/ with more test, I've found that trampoline didn't got built for windows :/ currently cmake didn't generate build rule for asm so its silently ignored(with msvc ide, but not ninja). we must have enable_language(ASM_MASM) to use ma...

I see. Thanks for clarifying. I'm Ok with merging these if Dean agrees, as I believe he's the code owner. Thanks, Hans On Thu, Jan 26, 2017 at 11:47 AM, Serge Rogatch <serge.rogatch at gmail.com> wrote: > There were no LLVM tests for presence of XRay instrumentation map in the > emitted assembly. You can see that https://reviews.llvm.org/D28624 adds this > check to the tests. > The tests in compiler-rt had been accidentally disabled. > https://reviews.llvm.org/D28623 enables them in > compiler-rt/test/xray/lit.cfg . > > On...

Hi Dean, For me the build is still broken: -- Builtin supported architectures: i386;x86_64;x86_64h CMake Error at projects/compiler-rt/lib/xray/tests/CMakeLists.txt:21 (add_library): add_library cannot create target "RTXRay.test.osx" because another target with the same name already exists. The existing target is a static library created in source directory "/Volumes/Transcend/code/llvm/projects/compiler-rt/lib/xray...