Displaying 5 results from an estimated 5 matches for "xray_fdr_logging".
2017 Mar 08
3
Use of the C++ standard library in XRay compiler-rt
...> 1 #include <thread>
> 2 #include <tuple>
> 1 #include <unordered_map>
> 1 #include <unordered_set>
> 3 #include <utility>
> I think the biggest part is containers, and they are mostly
> in ./xray_buffer_queue.h and ./xray_fdr_logging.cc.
>
> dependencies without buffer queue and fdr logging:
> ...compiler-rt/lib/xray % grep '#include <[^>.]*>' -oh `find . -type
> f|egrep -v 'tests|buffer|fdr'` | sort | uniq -c
> 9 #include <atomic>
> 4 #include <cassert>
>...
2017 Mar 15
2
Use of the C++ standard library in XRay compiler-rt
...;thread>
> > 2 #include <tuple>
> > 1 #include <unordered_map>
> > 1 #include <unordered_set>
> > 3 #include <utility>
> > I think the biggest part is containers, and they are mostly in
> ./xray_buffer_queue.h and ./xray_fdr_logging.cc.
>
> Yes, buffer_queue can definitely live without using system_error,
> unordered_map, and unordered_set. It might make it a bit more complex (we'd
> need to implement a correct and fairly efficient hash set) but if it means
> the deployment model is simpler then I'm happ...
2017 Mar 08
2
Use of the C++ standard library in XRay compiler-rt
So I stumbled across an issue that I think is a bit fundamental:
The xray runtime uses the C++ standard library.
This seems like a problem because whatever C++ standard library is used to
compile the XRay runtime may not be the same as the C++ standard library
(if any) that is used to build the target application and link XRay into.
Does this make sense? Is this a problem?
Talking to Chandler
2017 Mar 13
5
Use of the C++ standard library in XRay compiler-rt
...;thread>
> > 2 #include <tuple>
> > 1 #include <unordered_map>
> > 1 #include <unordered_set>
> > 3 #include <utility>
> > I think the biggest part is containers, and they are mostly in
> ./xray_buffer_queue.h and ./xray_fdr_logging.cc.
>
> Yes, buffer_queue can definitely live without using system_error,
> unordered_map, and unordered_set. It might make it a bit more complex (we'd
> need to implement a correct and fairly efficient hash set) but if it means
> the deployment model is simpler then I'm happ...
2018 Jun 28
2
XRay feature – pid reporting
I'm still somewhat unclear about what you mean by "metadata record entry at
the beginning of the block". I understand that I can make a MetadataRecord
that contains the pid/tid since a metadata record contains 16 bytes.
However, I don't understand what do you mean by the "beginning of the
block". Do you mean right after the file header?
My understanding is that at