Re: AutoFDO profile toolchain is open-sourced

2015-05-08 Thread Dehao Chen
On Fri, May 8, 2015 at 2:00 AM, Ilya Palachev wrote: > On 11.04.2015 01:49, Xinliang David Li wrote: >> >> On Fri, Apr 10, 2015 at 3:43 PM, Jan Hubicka wrote: LBR is used for both cfg edge profiling and indirect call Target value profiling. >>> >>> I see, that makes sense ;) I gue

Re: AutoFDO profile toolchain is open-sourced

2015-04-27 Thread Dehao Chen
On Mon, Apr 27, 2015 at 7:37 AM, Ilya Palachev wrote: > Hi, > > On 21.04.2015 20:25, Dehao Chen wrote: >> >> OTOH, the most important patch (insn-level discriminator support) is >> not in yet. Cary has just retired. Do you know if anyone would be >> interested in

Re: AutoFDO profile toolchain is open-sourced

2015-04-27 Thread Dehao Chen
On Thu, Apr 23, 2015 at 10:31 PM, Jan Hubicka wrote: > > > > It converts with the attached patches, but there's still some problem > > > parsing the data: > > > > > > % ./create_gcov -binary loop -gcov_version 1 -gcov loop.gcda > > > -gcov_version 0x500e > > > % gcc50 -O2 -fprofile-use loop.c >

Re: AutoFDO profile toolchain is open-sourced

2015-04-22 Thread Dehao Chen
Thanks, I'll forward the patches to quipper team. On Tue, Apr 21, 2015 at 8:47 PM, Andi Kleen wrote: > On Wed, Apr 22, 2015 at 05:15:47AM +0200, Andi Kleen wrote: >> On Tue, Apr 21, 2015 at 01:52:18PM -0700, Dehao Chen wrote: >> > Andi, >> > >> > Thanks

Re: AutoFDO profile toolchain is open-sourced

2015-04-21 Thread Dehao Chen
That's correct. For trunk, gcov_version is 0x1. We defined this as a flag so that you can actually change it via --gcov_version=0x1 instead of changing the code. Dehao On Tue, Apr 21, 2015 at 1:47 PM, Sebastian Pop wrote: > We also needed to adjust the gcov_version in autofdo/gcov.cc to read > 0

Re: AutoFDO profile toolchain is open-sourced

2015-04-21 Thread Dehao Chen
did a batch sync with quipper head. Please let me know if this solves the perf problem. Thanks, Dehao On Tue, Apr 21, 2015 at 10:36 AM, Andi Kleen wrote: > On Tue, Apr 21, 2015 at 10:27:49AM -0700, Dehao Chen wrote: >> In that case, we should get quipper fixed upstream to accomm

Re: AutoFDO profile toolchain is open-sourced

2015-04-21 Thread Dehao Chen
In that case, we should get quipper fixed upstream to accommodate new format. (Maybe they already fixed it, I will do a batch sync to make quipper up-to-date). Dehao On Tue, Apr 21, 2015 at 10:24 AM, Andi Kleen wrote: >> > BTW the biggest problem with autofdo currently is that it is >> > quite b

Re: AutoFDO profile toolchain is open-sourced

2015-04-21 Thread Dehao Chen
I'll get to it soon. When will stage1 close? OTOH, the most important patch (insn-level discriminator support) is not in yet. Cary has just retired. Do you know if anyone would be interested in porting insn-level discriminator support to trunk? Dehao On Tue, Apr 21, 2015 at 8:59 AM, Jan Hubicka

Re: AutoFDO profile toolchain is open-sourced

2015-04-21 Thread Dehao Chen
On Tue, Apr 21, 2015 at 7:25 AM, Andi Kleen wrote: > Ilya Palachev writes: >> >> But why create_gcov does not inform about that (no branch events were >> found)? It creates empty gcov file and says nothing :( >> >> Moreover, in the mentioned README it is said that perf should also be >> executed

Re: AutoFDO profile toolchain is open-sourced

2015-04-21 Thread Dehao Chen
On Tue, Apr 21, 2015 at 6:42 AM, Ilya Palachev wrote: > On 21.04.2015 14:57, Diego Novillo wrote: >> >> >From the autofdo page: https://github.com/google/autofdo >> >> [ ... ] >> Inputs: >> >> --profile: PERF_PROFILE collected using linux perf (with last branch >> record). >> In order to collect t

AutoFDO profile toolchain is open-sourced

2014-05-07 Thread Dehao Chen
We have open-sourced AutoFDO profile toolchain in: https://github.com/google/autofdo For GCC developers, the most important tool is create_gcov, which converts sampling based profile to GCC-readable profile. Please refer to the readme file (https://raw.githubusercontent.com/google/autofdo/master/

Re: Question about vectorization limit

2013-05-30 Thread Dehao Chen
modified. */ Dehao On Thu, May 30, 2013 at 12:03 PM, Toon Moene wrote: > On 05/30/2013 02:46 AM, Dehao Chen wrote: > >> In tree-vect-loop.c, it limits the vectorization only to loops that have 2 >> BBs: >> >>/* Inner-most loop. We currently require that the numbe

Question about vectorization limit

2013-05-29 Thread Dehao Chen
Hi, In tree-vect-loop.c, it limits the vectorization only to loops that have 2 BBs: /* Inner-most loop. We currently require that the number of BBs is exactly 2 (the header and latch). Vectorizable inner-most loops look like this: (pre-header)

Re: Possible headsup on GCC testsuite PCH failures

2012-09-23 Thread Dehao Chen
Yes, this is a known problem: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54645 A patch was proposed: http://gcc.gnu.org/ml/gcc-patches/2012-09/msg01563.html Sorry to break the test. Dehao On Sun, Sep 23, 2012 at 4:56 PM, Aaron Gray wrote: > Can someone double check this for me I am getting 99

Re: Compiler crash with block numbers

2012-09-20 Thread Dehao Chen
all I still check in this patch to fix the bootstrap problem? Thanks, Dehao On Fri, Sep 21, 2012 at 4:30 AM, Dehao Chen wrote: > IS_UNKNOWN_LOCATION checks if the source location is unknown. > == UNKNONW_LOCATION checks if source location is unknown and the block is > NULL. > > Yes,

Re: Compiler crash with block numbers

2012-09-20 Thread Dehao Chen
wrote: > On Thu, Sep 20, 2012 at 12:59 PM, Dehao Chen wrote: >> >> gcc/ChangeLog: >> tree-eh.c (lower_try_finally_dup_block): Use correct way to >> check unknown location. > > While you think about my questions, let's fix the bootstrap. This > patch is O

Re: Compiler crash with block numbers

2012-09-20 Thread Dehao Chen
wrote: > On Thu, Sep 20, 2012 at 11:46 AM, Dehao Chen wrote: >> Sure, I'll look into this problem today. >> >> Thanks, >> Dehao >> >> On Fri, Sep 21, 2012 at 2:25 AM, Ian Lance Taylor wrote: >>> Hi Dehao, I suspect that your recent patch ch

Re: Compiler crash with block numbers

2012-09-20 Thread Dehao Chen
Sure, I'll look into this problem today. Thanks, Dehao On Fri, Sep 21, 2012 at 2:25 AM, Ian Lance Taylor wrote: > Hi Dehao, I suspect that your recent patch changing block handling has > broken bootstrap with --enable-languages=go. I reduced the test case > to this C++ code: > > #include > > s

Re: [patch] Add a lexical block only when the callsite has source location info

2012-07-18 Thread Dehao Chen
On Wed, Jul 18, 2012 at 4:35 PM, Dodji Seketeli wrote: > Dehao Chen writes: > >> Hi, Dodji, >> >> Thanks for the comments. > > You are welcome. > > [...] > >> We difinitely need to modify the linemap to associate the pointer with >> the locat