search for: dehao

FWIW, I'm good with the updated data, but I'd really like at least someone from Apple and someone from ARM to chime in here... CC-ing random people in the hope it helps... On Mon, Feb 13, 2017 at 8:30 AM Dehao Chen via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Thanks for the comment. The performance experiments were performed on > Intel Sandybridge. Updated this info to the patch description. > > Dehao > On Sun, Feb 12, 2017 at 8:24 AM, Sanjay Patel <spatel at rotateright.c...

On 02/10/2017 05:21 PM, Dehao Chen wrote: > Thanks every for the comments. > > Do we have a decision here? You're good to go as far as I'm concerned. -Hal > > Dehao > > On Tue, Feb 7, 2017 at 10:24 PM, Hal Finkel <hfinkel at anl.gov > <mailto:hfinkel at anl.gov>> wrote: > &gt...

...s no need to wait for other issues to be fixed (minor issue). So you can move on with your patch. From: Agabaria, Mohammed Sent: Wednesday, June 07, 2017 15:24 To: Zaks, Ayal <ayal.zaks at intel.com>; Chandler Carruth <chandlerc at gmail.com>; Flamedoge <code.kchoi at gmail.com>; Dehao Chen <dehao at google.com> Cc: llvm-dev <llvm-dev at lists.llvm.org> Subject: RE: [llvm-dev] Enable vectorizer-maximize-bandwidth by default? Guys I have uploaded a fix on phabricator which fix the issue in SLM: https://reviews.llvm.org/D33983 From: Zaks, Ayal Sent: Tuesday, June 06,...

...t; > autcor00data_3 -77.00 % > > (on Atom) > > > > We still working on creating reproducers. > > In general we support this patch, just want to have a chance to > investigate the issues. We need a few days for that. > I mean, OK... but keep in mind that Dehao's original email went out over a week ago, so this patch has already been held up a while. As these benchmarks aren't readily available, we also can't do anything to help until a test case is posted. Have you considered contributing these benchmarks to the LLVM test suite? > >...

...important consideration, but the code size changes here seems small. > > Is the proposed change universal? Is there a way to undo it? All of the unrolling thresholds should be target-adjustable using the TTI::getUnrollingPreferences hook. -Hal > > On Tue, Feb 7, 2017 at 3:26 PM, Dehao Chen via llvm-dev > <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: > > Ping... with the updated code size impact data, any more comments? > Any more data that would be interesting to collect? > > Thanks, > Dehao > >...

Ping... with the updated code size impact data, any more comments? Any more data that would be interesting to collect? Thanks, Dehao On Thu, Feb 2, 2017 at 2:07 PM, Dehao Chen <dehao at google.com> wrote: > Here is the code size impact for clang, chrome and 24 google internal > benchmarks (name omited, 14 15 16 are encoding/decoding benchmarks similar > as h264). There are 2 columns, for threshold 300 and 450 re...

I had suggested having size metrics from somewhat larger applications such as Chrome, Webkit, or Firefox; clang itself; and maybe some of our internal binaries with rough size brackets? On Wed, Feb 1, 2017 at 4:33 PM Dehao Chen <dehao at google.com> wrote: > With the new data points, any comments on whether this can justify setting > fully inline threshold to 300 (or any other number) in O2? I can collect > more data points if it's helpful. > > Thanks, > Dehao > > On Tue, Jan 31, 20...

...ists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: > I had suggested having size metrics from somewhat larger applications such as Chrome, Webkit, or Firefox; clang itself; and maybe some of our internal binaries with rough size brackets? > > On Wed, Feb 1, 2017 at 4:33 PM Dehao Chen <dehao at google.com <mailto:dehao at google.com>> wrote: > With the new data points, any comments on whether this can justify setting fully inline threshold to 300 (or any other number) in O2? I can collect more data points if it's helpful. > > Thanks, > Dehao &gt...

...the attribute of the source (i.e trip count), and later design new extensible ways in dwarf to represent more context info? Adrian also suggested that we may need to consider have a flag or a separate debugging mode to indicate if we want to emit discriminator to prevent debug_line size increase. Dehao On Tue, Nov 1, 2016 at 9:34 PM, Dehao Chen <dehao at google.com> wrote: > > > On Tue, Nov 1, 2016 at 7:35 PM, Hal Finkel <hfinkel at anl.gov> wrote: > >> >> ------------------------------ >> >> *From: *"Dehao Chen" <dehao at google.com&...

...de, certainly in cases where line attribution is inherently ambiguous. In those cases, I have no problem with Just Doing It. Something likely to pad the line table to benefit profiling without similarly benefiting debugging… that's probably worth inventing a –gprofile or some such. I suspect Dehao's more elaborate ideas about discriminators fall into that category (although IIRC discriminators were invented mainly to benefit profiling in the first place, so maybe having discriminators at all would be something to put under a –gprofile kind of option). --paulr From: David Blaikie [mailto...

----- Original Message ----- > From: "Dehao Chen" <dehao at google.com> > To: "Hal Finkel" <hfinkel at anl.gov> > Cc: "llvm-dev" <llvm-dev at lists.llvm.org>, "Xinliang David Li" > <davidxl at google.com> > Sent: Tuesday, November 1, 2016 8:24:30 PM > Subject: Re: [llv...

...47.dealII 8.43% 450.soplex 2.41% 453.povray 5.40% 470.lbm 0.00% 482.sphinx3 7.10% 400.perlbench 2.77% 401.bzip2 9.62% 403.gcc 2.67% 429.mcf 9.54% 445.gobmk 7.40% 456.hmmer 9.79% 458.sjeng 9.98% 462.libquantum 10.90% 464.h264ref 30.21% 471.omnetpp 0.52% 473.astar 5.67% 483.xalancbmk 1.46% mean 7.86% Dehao On Thu, Oct 27, 2016 at 11:55 AM, Xinliang David Li <davidxl at google.com> wrote: > Do you have an estimate of the debug_line size increase? I guess it will > be small. > > David > > On Thu, Oct 27, 2016 at 11:39 AM, Dehao Chen <dehao at google.com> wrote: > >...

----- Original Message ----- > From: "Dehao Chen" <dehao at google.com> > To: "Hal Finkel" <hfinkel at anl.gov> > Cc: "llvm-dev" <llvm-dev at lists.llvm.org>, "Xinliang David Li" > <davidxl at google.com> > Sent: Tuesday, November 1, 2016 6:41:29 PM > Subject: Re: [llv...

damn... my english is not readable at all when I try to write fast... trying to make some clarification below, hopefully can make it more readable... On Tue, Nov 1, 2016 at 2:07 PM, Dehao Chen <dehao at google.com> wrote: > Oops... pressed the wrong button and sent out early... > > On Tue, Nov 1, 2016 at 2:01 PM, Dehao Chen <dehao at google.com> wrote: > >> If Hal's proposal is for SamplePGO purpose, let me clarify some design >> principles o...

...7:49 PM Subject: buildbot failure in LLVM on clang-cmake-mips To: Adrian Prantl <aprantl at apple.com>, Ahmed Bougacha < ahmed.bougacha at gmail.com>, Bob Wilson <bob.wilson at apple.com>, David Blaikie <dblaikie at gmail.com>, Davide Italiano <davide at freebsd.org>, Dehao Chen < dehao at google.com> Cc: gkistanova at gmail.com The Buildbot has detected a new failure on builder clang-cmake-mips while building llvm. Full details are available at: http://lab.llvm.org:8011/builders/clang-cmake-mips/builds/9538 Buildbot URL: http://lab.llvm.org:8011/ Buildslav...

----- Original Message ----- > From: "Hal Finkel via llvm-dev" <llvm-dev at lists.llvm.org> > To: "Dehao Chen" <dehao at google.com> > Cc: "llvm-dev" <llvm-dev at lists.llvm.org>, "Xinliang David Li" > <davidxl at google.com> > Sent: Tuesday, November 1, 2016 4:26:17 PM > Subject: Re: [llvm-dev] (RFC) Encoding code duplication factor in > discr...

The large percentages are from those tiny benchmarks. If you look at omnetpp (0.52%), and xalanc (1.46%), the increase is small. To get a better average increase, you can sum up total debug_line size before and after and compute percentage accordingly. David On Thu, Oct 27, 2016 at 1:11 PM, Dehao Chen <dehao at google.com> wrote: > The impact to debug_line is actually not small. I only implemented the > part 1 (encoding duplication factor) for loop unrolling and loop > vectorization. The debug_line size overhead for "-O2 -g1" binary of speccpu > C/C++ benchmarks...

...is used to represent the profile. I am still tuning the performance to fill in the gap. During the meantime, we encourage you to try it out. Bug reports/fixes are always welcome. For more information about how to generate AutoFDO profile, please refer to https://github.com/google/autofdo Cheers, Dehao -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20151009/a22fa364/attachment.html>

On Fri, May 19, 2017 at 4:01 PM Adam Nemet via llvm-dev < llvm-dev at lists.llvm.org> wrote: > I will run it on Cyclone/AArch64 next week. > FYI, we're still waiting on these Adam... -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170530/7cb390ca/attachment.html>

....llvm.org> Date: Wed, Sep 30, 2015 at 11:34 PM Subject: buildbot failure in LLVM on llvm-mips-linux To: Ahmed Bougacha <ahmed.bougacha at gmail.com>, Chad Rosier < mcrosier at codeaurora.org>, David Blaikie <dblaikie at gmail.com>, Davide Italiano <davide at freebsd.org>, Dehao Chen <dehao at google.com>, Evgeniy Stepanov <eugeni.stepanov at gmail.com>, Hal Finkel <hfinkel at anl.gov>, Kostya Serebryany <kcc at google.com>, Michael Zolotukhin <mzolotukhin at apple.com>, Reid Kleckner <rnk at google.com>, Sanjay Patel <spatel at rotat...