en Copyright 2015 Java http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/tools/llvm-xray/X86/stack-empty-case.yaml#d14d54ba Fix llvm-xray tests to avoid subshellsWe already uses pipefail to detect failure of a redirected command, sothe "|| echo failure" construct was unnecessary.These tests run and pass on Windows now.llvm-svn: 312747 List of files: /llvm-project-15.0.7/llvm/test/tools/llvm-xray/X86/stack-empty-case.yaml Thu, 07 Sep 2017 21:28:09 +0000 Reid Kleckner <rnk@google.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/tools/llvm-xray/X86/stack-empty-case.yaml#7248a8bc [XRay][tools] Disable windows for tests that use an unsupported shell redirect.The tests are filechecking against stderr and use some magic to make stdout goaway and pipe stderr to FileCheck. This broke bots on windows.llvm-svn: 312739 List of files: /llvm-project-15.0.7/llvm/test/tools/llvm-xray/X86/stack-empty-case.yaml Thu, 07 Sep 2017 19:10:34 +0000 Keith Wyss <wyssman@gmail.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/tools/llvm-xray/X86/stack-empty-case.yaml#9420ec33 [XRay][tools] Function call stack based analysis tooling for XRay tracesSecond try after fixing a code san problem with iterator reference types.This change introduces a subcommand to the llvm-xray tool called"stacks" which allows for analysing XRay traces provided as inputs andaccounting time to stacks instead of just individual functions. Thisgives us a more precise view of where in a program the latency isactually attributed.The tool uses a trie data structure to keep track of the caller-calleerelationships as we process the XRay traces. In particular, we keeptrack of the function call stack as we enter functions. While we'redoing this we're adding nodes in a trie and indicating a "calls"relatinship between the caller (current top of the stack) and the callee(the new top of the stack). When we push function ids onto the stack, wekeep track of the timestamp (TSC) for the enter event.When exiting functions, we are able to account the duration by gettingthe difference between the timestamp of the exit event and thecorresponding entry event in the stack. This works even if we somehowmiss the exit events for intermediary functions (i.e. if the exit eventis not cleanly associated with the enter event at the top of the stack).The output of the tool currently provides just the top N leaf functionsthat contribute the most latency, and the top N stacks that have themost frequency. In the future we can provide more sophisticated querymechanisms and potentially an export to database feature to make offlineanalysis of the stack traces possible with existing tools.Differential revision: D34863llvm-svn: 312733 List of files: /llvm-project-15.0.7/llvm/test/tools/llvm-xray/X86/stack-empty-case.yaml Thu, 07 Sep 2017 18:07:48 +0000 Keith Wyss <wyssman@gmail.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/tools/llvm-xray/X86/stack-empty-case.yaml#4c12c782 [XRay][tools] Function call stack based analysis tooling for XRay tracesThis change introduces a subcommand to the llvm-xray tool called"stacks" which allows for analysing XRay traces provided as inputs andaccounting time to stacks instead of just individual functions. Thisgives us a more precise view of where in a program the latency isactually attributed.The tool uses a trie data structure to keep track of the caller-calleerelationships as we process the XRay traces. In particular, we keeptrack of the function call stack as we enter functions. While we'redoing this we're adding nodes in a trie and indicating a "calls"relatinship between the caller (current top of the stack) and the callee(the new top of the stack). When we push function ids onto the stack, wekeep track of the timestamp (TSC) for the enter event.When exiting functions, we are able to account the duration by gettingthe difference between the timestamp of the exit event and thecorresponding entry event in the stack. This works even if we somehowmiss the exit events for intermediary functions (i.e. if the exit eventis not cleanly associated with the enter event at the top of the stack).The output of the tool currently provides just the top N leaf functionsthat contribute the most latency, and the top N stacks that have themost frequency. In the future we can provide more sophisticated querymechanisms and potentially an export to database feature to make offlineanalysis of the stack traces possible with existing tools.llvm-svn: 312426 List of files: /llvm-project-15.0.7/llvm/test/tools/llvm-xray/X86/stack-empty-case.yaml Sun, 03 Sep 2017 00:03:47 +0000 Keith Wyss <wyssman@gmail.com>