search for: __xray_instr_map

Displaying 5 results from an estimated 5 matches for "__xray_instr_map".

2016 Jun 23
2
Building an array in a section from multiple object files
...single symbol (or two, one to mark the start and the other to mark the end). I'm trying to get this to work initially on x86 and Linux (ELF). What I've got currently in http://reviews.llvm.org/D19904 creates this section (.xray_instr_map) and defines two globals in that section named "__xray_instr_map" and "__xray_instr_map_end". The problem inevitably with this approach is that having multiple object files have these definitions cause issues with multiple definition violations at link time. I *think* the solution involves having COMDAT sections per-function that has the instrume...
2016 Jun 23
2
Building an array in a section from multiple object files
...>> other to mark the end). I'm trying to get this to work initially on x86 and >> Linux (ELF). >> >> What I've got currently in http://reviews.llvm.org/D19904 creates this >> section (.xray_instr_map) and defines two globals in that section named >> "__xray_instr_map" and "__xray_instr_map_end". The problem inevitably with >> this approach is that having multiple object files have these definitions >> cause issues with multiple definition violations at link time. >> >> I *think* the solution involves having COMDAT sections...
2016 Jun 27
0
Building an array in a section from multiple object files
...rk the end). I'm trying to get this to work initially on x86 and >>> Linux (ELF). >>> >>> What I've got currently in http://reviews.llvm.org/D19904 creates this >>> section (.xray_instr_map) and defines two globals in that section named >>> "__xray_instr_map" and "__xray_instr_map_end". The problem inevitably with >>> this approach is that having multiple object files have these definitions >>> cause issues with multiple definition violations at link time. >>> >>> I *think* the solution involves having...
2016 Jun 27
1
Building an array in a section from multiple object files
...trying to get this to work initially on x86 and >>>> Linux (ELF). >>>> >>>> What I've got currently in http://reviews.llvm.org/D19904 creates this >>>> section (.xray_instr_map) and defines two globals in that section named >>>> "__xray_instr_map" and "__xray_instr_map_end". The problem inevitably with >>>> this approach is that having multiple object files have these definitions >>>> cause issues with multiple definition violations at link time. >>>> >>>> I *think* the solution...
2016 Jun 28
2
XRay: Demo on x86_64/Linux almost done; some questions.
...6-28 17:30:34] dberris at dberris: ~/xray/llvm-build% ./bin/clang -c other.cc -x c++ -std=c++11 -fxray-instrument [16-06-28 17:30:46] dberris at dberris: ~/xray/llvm-build% ./bin/clang -o test.bin test.o other.o -fxray-instrument [16-06-28 17:30:55] dberris at dberris: ~/xray/llvm-build% ./test.bin __xray_instr_map at 0x400f5b..0x400fdb 400cf0 E * @function(400cf0) 400d1c X * @function(400cf0) 400da0 E * @function(400da0) 400dcc X * @function(400da0) main has started. Not instrumented 4133: [9699491610577808] E1 Hello, XRay! 4133: [9699491610592074] X1 4133:...