search for: d21612

Thanks Nirav, I can confirm that this works when I do the compile with llc, but then when linking to an executable with clang (patched with http://reviews.llvm.org/D20352 and compiler-rt patched with http://reviews.llvm.org/D21612) on Linux, I'm getting something different. Here's a sample of the transcript, and what I'm seeing: --->8 clang invocation 8<--- [16-06-23 3:33:42] dberris at dberris: ~/xray/llvm-build% ./bin/clang -fxray-instrument -x c++ -std=c++11 -o test.bin test.cc -g --verbose clang versio...

...patches under review that when applied cleanly to LLVM and compiler-rt allows for building applications with XRay tracing enabled on Linux binaries from start to end. The list of patches to apply are: * https://reviews.llvm.org/D21987 (accounting tool, lives in llvm) * https://reviews.llvm.org/D21612 then https://reviews.llvm.org/D21982 (compiler-rt XRay runtime implementation) To test this out, I built clang with XRay and ran it on a hello world application. Here's how I did it: 1) Build clang+compiler-rt with the above patches patched in. Follow the normal instructions for getting a ver...

Hi, The following three patches, when applied cleanly to LLVM+Clang+compiler-rt will now allow for building and running binaries with a very simple version of XRay included: http://reviews.llvm.org/D21612 (compiler-rt) http://reviews.llvm.org/D20352 (clang) http://reviews.llvm.org/D19904 (llvm) To use this on x86_64-unknown-linux-gnu you'd need to set the flags '-fxray-instrument' and if you'd like to instrument all functions, set '-fxray-instruction-threshold=1'. Apply thos...

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

...Berris <dberris at google.com> wrote: > Thanks Nirav, > > I can confirm that this works when I do the compile with llc, but then > when linking to an executable with clang (patched with > http://reviews.llvm.org/D20352 and compiler-rt patched with > http://reviews.llvm.org/D21612) on Linux, I'm getting something > different. Here's a sample of the transcript, and what I'm seeing: > > --->8 clang invocation 8<--- > [16-06-23 3:33:42] dberris at dberris: ~/xray/llvm-build% ./bin/clang > -fxray-instrument -x c++ -std=c++11 -o test.bin test.cc -...

...ttp://lists.llvm.org/pipermail/llvm-dev/2016-April/098901.html [1] There are three patches that implement the prototype XRay implementation, updated to track trunk of LLVM, Clang, and compiler-rt: http://reviews.llvm.org/D19904 (llvm) http://reviews.llvm.org/D20352 (clang) http://reviews.llvm.org/D21612 (compiler-rt) [2] XRay: A Function Call Tracing System: http://research.google.com/pubs/pub45287.html -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160704/05c7027e/attachment.html>

Hmm. Odd. I just rebuilt from scratch and it seems to work with the test/CodeGen/X86/xray-attribute-instrumentation.ll test case outputing straight to obj: llc -filetype=obj -o ~/a.o -mtriple=x86_64-apple-macosx < test/CodeGen/X86/xray-attribute-instrumentation.ll What test case are you using? In any case, the issue appears to be that llvm doesn't realize that the target address is

On Wed, Jun 22, 2016 at 6:05 AM Nirav Davé <niravd at google.com> wrote: > This appears to work: > > auto Target = OutContext.createLinkerPrivateTempSymbol(); > > with > > auto Target = OutContext.createTempSymbol(); > > -Nirav > > Thanks Nirav -- I tried this but I'm still getting a "jmpq <address>" with this incantation when I load and