<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Any progress here?
- Rick in Analyzers</title>
    <link>https://community.intel.com/t5/Analyzers/Call-stack-mechanism-implementation-question/m-p/1030015#M13305</link>
    <description>&lt;P&gt;Any progress here?&lt;/P&gt;

&lt;P&gt;- Rick&lt;/P&gt;</description>
    <pubDate>Wed, 25 Feb 2015 23:11:20 GMT</pubDate>
    <dc:creator>Richard_H_1</dc:creator>
    <dc:date>2015-02-25T23:11:20Z</dc:date>
    <item>
      <title>Call stack mechanism implementation question</title>
      <link>https://community.intel.com/t5/Analyzers/Call-stack-mechanism-implementation-question/m-p/1030009#M13299</link>
      <description>&lt;P&gt;I am running a Go program with dwarf information and VTune does a good job figuring out line numbers and so forth but it struggles with stack walks. I am guessing that it is because Go's stack conventions, how Go uses EBP for example, are different than those supported by Vtune. Is there a document or some sort of clue sheet about what Vtune expects from the stack formats? Also can anyone think of a work around that doesn't require Go changing its conventions.&lt;/P&gt;</description>
      <pubDate>Fri, 19 Dec 2014 21:26:40 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Call-stack-mechanism-implementation-question/m-p/1030009#M13299</guid>
      <dc:creator>Richard_H_1</dc:creator>
      <dc:date>2014-12-19T21:26:40Z</dc:date>
    </item>
    <item>
      <title>Did you mean VTune stack</title>
      <link>https://community.intel.com/t5/Analyzers/Call-stack-mechanism-implementation-question/m-p/1030010#M13300</link>
      <description>&lt;P&gt;Did you mean VTune stack sampling failed on Go program? Dwarf format is supported by VTune, as well as its calling convention (both for C/C++ and Fortran).&lt;/P&gt;

&lt;P&gt;Can you provide Go program or other test case so I can verify this issue?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 20 Dec 2014 03:51:30 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Call-stack-mechanism-implementation-question/m-p/1030010#M13300</guid>
      <dc:creator>Peter_W_Intel</dc:creator>
      <dc:date>2014-12-20T03:51:30Z</dc:date>
    </item>
    <item>
      <title>Since December we taught our</title>
      <link>https://community.intel.com/t5/Analyzers/Call-stack-mechanism-implementation-question/m-p/1030011#M13301</link>
      <description>&lt;P&gt;Since December we taught our go compiler about base pointers but we are still having problems with VTune. &lt;SPAN style="font-size: 1em; line-height: 1.5;"&gt;Not sure what to do next. I uploaded bench.tar which holds a program we compiled using the latest go compiler from golang.org built with a the environment variable GOEXPERIMENT=framepointer &amp;nbsp;which tells the compiler to generate base pointers. You can build such a system using the instructions at golang.org for building the latest development branch.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;

&lt;P&gt;&lt;SPAN style="font-size: 1em; line-height: 1.5;"&gt;I uploaded a binary built with the system in the bench.tar file.&lt;/SPAN&gt;&lt;/P&gt;

&lt;P&gt;To run bench simply extract it from the bench.tar file and execute ./bench -bench=garbage. Below is what to expect. When we run this in Vtune &amp;gt;90% of the stackframes are not recognized but oddly enough some are and those seem correct. Sometimes the call stacks are also correct but not always. We have other internal performance tools and gdb working that rely on our dwarf info so somehow vtune wants more/different information than gdb. Any clues would be appreciated.&lt;/P&gt;

&lt;P&gt;Here is what to expect from the ./bench file in the tar file.&lt;/P&gt;

&lt;P&gt;rlh@rlh0:~/work/code/src/golang.org/x/benchmarks/bench/xxx$ &lt;STRONG&gt;./bench -bench=garbage -benchnum=1&lt;/STRONG&gt;&lt;BR /&gt;
	consumption=1829KB npkg=14&lt;BR /&gt;
	2015/02/11 14:38:32 Benchmarking 1 iterations&lt;BR /&gt;
	2015/02/11 14:38:32 Benchmarking 100 iterations&lt;BR /&gt;
	2015/02/11 14:38:35 Benchmarking 500 iterations&lt;BR /&gt;
	2015/02/11 14:38:50 Result: {N:500 Duration:14.95397866s RunTime:29907957 Metrics:map[virtual-mem:324300800 rss:88551424 allocated:3130122 sys-total:98429240 sys-gc:5436275 gc-pause-total:1011241 sys-other:6354373 gc-pause-one:5378946 time:29907957 cputime:29936444 allocs:68124 sys-heap:86409216 sys-stack:229376] Files:map[cpuprof:/tmp/8.cpuprof memprof:/tmp/9.memprof memprof0:/tmp/7.memprof]}&lt;BR /&gt;
	GOPERF-METRIC:allocated=3130122&lt;BR /&gt;
	GOPERF-METRIC:allocs=68124&lt;BR /&gt;
	GOPERF-METRIC:cputime=29936444&lt;BR /&gt;
	GOPERF-METRIC:gc-pause-one=5378946&lt;BR /&gt;
	GOPERF-METRIC:gc-pause-total=1011241&lt;BR /&gt;
	GOPERF-METRIC:rss=88551424&lt;BR /&gt;
	GOPERF-METRIC:sys-gc=5436275&lt;BR /&gt;
	GOPERF-METRIC:sys-heap=86409216&lt;BR /&gt;
	GOPERF-METRIC:sys-other=6354373&lt;BR /&gt;
	GOPERF-METRIC:sys-stack=229376&lt;BR /&gt;
	GOPERF-METRIC:sys-total=98429240&lt;BR /&gt;
	GOPERF-METRIC:time=29907957&lt;BR /&gt;
	GOPERF-METRIC:virtual-mem=324300800&lt;BR /&gt;
	GOPERF-FILE:cpuprof=/tmp/10.prof.txt&lt;BR /&gt;
	GOPERF-FILE:memprof=/tmp/11.prof.txt&lt;BR /&gt;
	GC: #70 116534366ns @700793116853489 pause=21789741 maxpause=28947825 goroutines=1036 gomaxprocs=1&lt;BR /&gt;
	GC: &amp;nbsp; &amp;nbsp; sweep term: 62842ns&amp;nbsp;&amp;nbsp; &amp;nbsp;max=88444&amp;nbsp;&amp;nbsp; &amp;nbsp;total=3790648&amp;nbsp;&amp;nbsp; &amp;nbsp;procs=1&lt;BR /&gt;
	GC: &amp;nbsp; &amp;nbsp; scan: &amp;nbsp; &amp;nbsp; &amp;nbsp; 318526ns&amp;nbsp;&amp;nbsp; &amp;nbsp;max=1840104&amp;nbsp;&amp;nbsp; &amp;nbsp;total=57351939&amp;nbsp;&amp;nbsp; &amp;nbsp;procs=1&lt;BR /&gt;
	GC: &amp;nbsp; &amp;nbsp; install wb: 1573ns&amp;nbsp;&amp;nbsp; &amp;nbsp;max=3040&amp;nbsp;&amp;nbsp; &amp;nbsp;total=122680&amp;nbsp;&amp;nbsp; &amp;nbsp;procs=1&lt;BR /&gt;
	GC: &amp;nbsp; &amp;nbsp; mark: &amp;nbsp; &amp;nbsp; &amp;nbsp; 94426099ns&amp;nbsp;&amp;nbsp; &amp;nbsp;max=98579167&amp;nbsp;&amp;nbsp; &amp;nbsp;total=5672118299&amp;nbsp;&amp;nbsp; &amp;nbsp;procs=1&lt;BR /&gt;
	GC: &amp;nbsp; &amp;nbsp; mark term: &amp;nbsp;21725326ns&amp;nbsp;&amp;nbsp; &amp;nbsp;max=28947825&amp;nbsp;&amp;nbsp; &amp;nbsp;total=1319757727&amp;nbsp;&amp;nbsp; &amp;nbsp;procs=1&lt;BR /&gt;
	rlh@rlh0:~/work/code/src/golang.org/x/benchmarks/bench/xxx$&amp;nbsp;&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 11 Feb 2015 19:58:00 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Call-stack-mechanism-implementation-question/m-p/1030011#M13301</guid>
      <dc:creator>Richard_H_1</dc:creator>
      <dc:date>2015-02-11T19:58:00Z</dc:date>
    </item>
    <item>
      <title>Thank you for test case, is</title>
      <link>https://community.intel.com/t5/Analyzers/Call-stack-mechanism-implementation-question/m-p/1030012#M13302</link>
      <description>&lt;P&gt;Thank you for test case, is there any dependency for environment to run?&lt;/P&gt;

&lt;P&gt;# ./bench -bench=garbage -benchnum=1 consumption=1829KB npkg=14&lt;BR /&gt;
	parse /usr/local/&lt;STRONG&gt;google/home/rlh/work/go/src/net/http&lt;/STRONG&gt; open /usr/local/google/home/rlh/work/go/src/net/http: no such file or directory&lt;BR /&gt;
	panic: fail&lt;/P&gt;

&lt;P&gt;goroutine 1 [running]:&lt;BR /&gt;
	golang.org/x/benchmarks/garbage.parsePackage(0x6c3160)&lt;BR /&gt;
	&amp;nbsp;&amp;nbsp; &amp;nbsp;/usr/local/google/home/rlh/work/code/src/golang.org/x/benchmarks/garbage/garbage.go:136 +0x3d7&lt;/P&gt;

&lt;P&gt;......&lt;/P&gt;

&lt;P&gt;I have no "google" sub-directory under /usr/local, what should software be installed? and where? &amp;nbsp;&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 12 Feb 2015 07:27:15 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Call-stack-mechanism-implementation-question/m-p/1030012#M13302</guid>
      <dc:creator>Peter_W_Intel</dc:creator>
      <dc:date>2015-02-12T07:27:15Z</dc:date>
    </item>
    <item>
      <title>Sorry, the garbage benchmark</title>
      <link>https://community.intel.com/t5/Analyzers/Call-stack-mechanism-implementation-question/m-p/1030013#M13303</link>
      <description>&lt;P&gt;Sorry, the garbage benchmark reads from a directory in the standard go source tree. The splay should be self contained.&lt;/P&gt;

&lt;P&gt;rlh@rlh0:~/xbenchx$ &lt;STRONG&gt;./bench -bench=splay&lt;/STRONG&gt;&lt;BR /&gt;
	2015/02/12 10:00:46 Benchmarking 1 iterations&lt;BR /&gt;
	2015/02/12 10:00:47 Benchmarking 100 iterations&lt;BR /&gt;
	2015/02/12 10:00:48 Benchmarking 2000 iterations&lt;BR /&gt;
	2015/02/12 10:01:02 Result: {N:2000 Duration:13.763610345s RunTime:6881805 Metrics:map[virtual-mem:208637952 rss:94838784 cputime:6962112 allocated:541428 allocs:10404 sys-total:103431216 sys-gc:5745011 time:6881805 sys-other:6132413 sys-stack:196608 gc-pause-total:358926 gc-pause-one:3901374 sys-heap:91357184] Files:map[memprof0:/tmp/7.memprof cpuprof:/tmp/8.cpuprof memprof:/tmp/9.memprof]}&lt;BR /&gt;
	2015/02/12 10:01:02 Benchmarking 1 iterations&lt;BR /&gt;
	2015/02/12 10:01:02 Benchmarking 100 iterations&lt;BR /&gt;
	2015/02/12 10:01:03 Benchmarking 1000 iterations&lt;BR /&gt;
	2015/02/12 10:01:10 Result: {N:1000 Duration:6.669404447s RunTime:6669404 Metrics:map[virtual-mem:217206784 cputime:6933084 allocs:10409 sys-total:112000048 sys-heap:99418112 sys-stack:196608 time:6669404 rss:110415872 allocated:542357 gc-pause-total:356282 sys-gc:6244723 sys-other:6140605 gc-pause-one:3958692] Files:map[memprof0:/tmp/16.memprof cpuprof:/tmp/17.cpuprof memprof:/tmp/18.memprof]}&lt;BR /&gt;
	2015/02/12 10:01:10 Benchmarking 1 iterations&lt;BR /&gt;
	2015/02/12 10:01:11 Benchmarking 100 iterations&lt;BR /&gt;
	2015/02/12 10:01:12 Benchmarking 2000 iterations&lt;BR /&gt;
	2015/02/12 10:01:26 Result: {N:2000 Duration:13.481776002s RunTime:6740888 Metrics:map[allocs:10404 sys-total:120577072 sys-heap:107479040 gc-pause-total:349784 sys-gc:6752627 sys-other:6148797 gc-pause-one:3974827 time:6740888 virtual-mem:225783808 rss:119345152 cputime:6820730 allocated:541250 sys-stack:196608] Files:map[memprof0:/tmp/25.memprof cpuprof:/tmp/26.cpuprof memprof:/tmp/27.memprof]}&lt;BR /&gt;
	2015/02/12 10:01:26 Benchmarking 1 iterations&lt;BR /&gt;
	2015/02/12 10:01:26 Benchmarking 100 iterations&lt;BR /&gt;
	2015/02/12 10:01:27 Benchmarking 2000 iterations&lt;BR /&gt;
	2015/02/12 10:01:41 Result: {N:2000 Duration:13.651746167s RunTime:6825873 Metrics:map[sys-heap:107479040 sys-stack:196608 sys-gc:6752627 sys-other:6148797 time:6825873 rss:119603200 allocs:10404 sys-total:120577072 gc-pause-one:3977067 virtual-mem:225783808 cputime:6904047 allocated:543145 gc-pause-total:353959] Files:map[memprof:/tmp/36.memprof memprof0:/tmp/34.memprof cpuprof:/tmp/35.cpuprof]}&lt;BR /&gt;
	2015/02/12 10:01:41 Benchmarking 1 iterations&lt;BR /&gt;
	2015/02/12 10:01:41 Benchmarking 100 iterations&lt;BR /&gt;
	2015/02/12 10:01:43 Benchmarking 2000 iterations&lt;BR /&gt;
	2015/02/12 10:01:57 Result: {N:2000 Duration:13.743759372s RunTime:6871879 Metrics:map[allocs:10404 sys-heap:107479040 gc-pause-total:355820 gc-pause-one:3953562 time:6871879 rss:119603200 cputime:6953678 allocated:541561 sys-total:120577072 sys-stack:196608 sys-gc:6752627 sys-other:6148797 virtual-mem:225783808] Files:map[memprof0:/tmp/43.memprof cpuprof:/tmp/44.cpuprof memprof:/tmp/45.memprof]}&lt;BR /&gt;
	Count=760400 Total=6.3791752639e+10 Min=11674 Mean=83892.36275512994 RMS=2.7770491889907755e+06 Max=1.48924784e+08 StdDev=2.775783565470609e+06&lt;BR /&gt;
	GOPERF-METRIC:allocated=542357&lt;BR /&gt;
	GOPERF-METRIC:allocs=10409&lt;BR /&gt;
	GOPERF-METRIC:cputime=6933084&lt;BR /&gt;
	GOPERF-METRIC:gc-pause-one=3958692&lt;BR /&gt;
	GOPERF-METRIC:gc-pause-total=356282&lt;BR /&gt;
	GOPERF-METRIC:rss=119603200&lt;BR /&gt;
	GOPERF-METRIC:sys-gc=6752627&lt;BR /&gt;
	GOPERF-METRIC:sys-heap=107479040&lt;BR /&gt;
	GOPERF-METRIC:sys-other=6148797&lt;BR /&gt;
	GOPERF-METRIC:sys-stack=196608&lt;BR /&gt;
	GOPERF-METRIC:sys-total=120577072&lt;BR /&gt;
	GOPERF-METRIC:time=6669404&lt;BR /&gt;
	GOPERF-METRIC:virtual-mem=217206784&lt;BR /&gt;
	GOPERF-FILE:cpuprof=/tmp/46.prof.txt&lt;BR /&gt;
	GOPERF-FILE:memprof=/tmp/47.prof.txt&lt;BR /&gt;
	GC: #472 115296766ns @770579699027981 pause=17217886 maxpause=19372756 goroutines=12 gomaxprocs=1&lt;BR /&gt;
	GC: &amp;nbsp; &amp;nbsp; sweep term: 93399ns&amp;nbsp;&amp;nbsp; &amp;nbsp;max=93399&amp;nbsp;&amp;nbsp; &amp;nbsp;total=23879494&amp;nbsp;&amp;nbsp; &amp;nbsp;procs=1&lt;BR /&gt;
	GC: &amp;nbsp; &amp;nbsp; scan: &amp;nbsp; &amp;nbsp; &amp;nbsp; 259286ns&amp;nbsp;&amp;nbsp; &amp;nbsp;max=512635&amp;nbsp;&amp;nbsp; &amp;nbsp;total=101556244&amp;nbsp;&amp;nbsp; &amp;nbsp;procs=1&lt;BR /&gt;
	GC: &amp;nbsp; &amp;nbsp; install wb: 2033ns&amp;nbsp;&amp;nbsp; &amp;nbsp;max=5115&amp;nbsp;&amp;nbsp; &amp;nbsp;total=714122&amp;nbsp;&amp;nbsp; &amp;nbsp;procs=1&lt;BR /&gt;
	GC: &amp;nbsp; &amp;nbsp; mark: &amp;nbsp; &amp;nbsp; &amp;nbsp; 97819594ns&amp;nbsp;&amp;nbsp; &amp;nbsp;max=124489478&amp;nbsp;&amp;nbsp; &amp;nbsp;total=43965078834&amp;nbsp;&amp;nbsp; &amp;nbsp;procs=1&lt;BR /&gt;
	GC: &amp;nbsp; &amp;nbsp; mark term: &amp;nbsp;17122454ns&amp;nbsp;&amp;nbsp; &amp;nbsp;max=19372756&amp;nbsp;&amp;nbsp; &amp;nbsp;total=7429728046&amp;nbsp;&amp;nbsp; &amp;nbsp;procs=1&lt;BR /&gt;
	rlh@rlh0:~/xbenchx$&amp;nbsp;&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 12 Feb 2015 15:10:51 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Call-stack-mechanism-implementation-question/m-p/1030013#M13303</guid>
      <dc:creator>Richard_H_1</dc:creator>
      <dc:date>2015-02-12T15:10:51Z</dc:date>
    </item>
    <item>
      <title>Thank you to correct this</title>
      <link>https://community.intel.com/t5/Analyzers/Call-stack-mechanism-implementation-question/m-p/1030014#M13304</link>
      <description>&lt;P&gt;Thank you to correct this usage. Now, I can reproduce this issue -&lt;/P&gt;

&lt;P&gt;# amplxe-cl -collect advanced-hotspots -knob collection-detail=stack-sampling -d 60 ./bench -bench=splay&lt;/P&gt;

&lt;P&gt;There is no call stack info in bottom-up report, I will report the developer and get back to you as soon as I can.&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 13 Feb 2015 02:25:58 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Call-stack-mechanism-implementation-question/m-p/1030014#M13304</guid>
      <dc:creator>Peter_W_Intel</dc:creator>
      <dc:date>2015-02-13T02:25:58Z</dc:date>
    </item>
    <item>
      <title>Any progress here?
- Rick</title>
      <link>https://community.intel.com/t5/Analyzers/Call-stack-mechanism-implementation-question/m-p/1030015#M13305</link>
      <description>&lt;P&gt;Any progress here?&lt;/P&gt;

&lt;P&gt;- Rick&lt;/P&gt;</description>
      <pubDate>Wed, 25 Feb 2015 23:11:20 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Call-stack-mechanism-implementation-question/m-p/1030015#M13305</guid>
      <dc:creator>Richard_H_1</dc:creator>
      <dc:date>2015-02-25T23:11:20Z</dc:date>
    </item>
    <item>
      <title>Our developer said, adding</title>
      <link>https://community.intel.com/t5/Analyzers/Call-stack-mechanism-implementation-question/m-p/1030016#M13306</link>
      <description>&lt;P&gt;Our developer said, adding support for "Go" calling convention and call stack mechanism is a new feature request. I will put any update - if it will be ready...but it is hard to give a detail time frame. Thanks for your understandings!&lt;/P&gt;</description>
      <pubDate>Thu, 26 Feb 2015 07:18:16 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Call-stack-mechanism-implementation-question/m-p/1030016#M13306</guid>
      <dc:creator>Peter_W_Intel</dc:creator>
      <dc:date>2015-02-26T07:18:16Z</dc:date>
    </item>
  </channel>
</rss>

