From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 54652 invoked by alias); 25 Oct 2016 14:32:12 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Received: (qmail 53433 invoked by uid 89); 25 Oct 2016 14:32:11 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_PASS autolearn=ham version=3.3.2 spammy=wind, counter, Hx-languages-length:924 X-HELO: mx2.suse.de Received: from mx2.suse.de (HELO mx2.suse.de) (195.135.220.15) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 25 Oct 2016 14:32:05 +0000 Received: from relay2.suse.de (charybdis-ext.suse.de [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id 8C8B5AAB9; Tue, 25 Oct 2016 14:32:00 +0000 (UTC) Subject: Re: [RFC] Speed-up -fprofile-update=atomic To: Richard Biener References: <1253ac69-3301-f185-e43a-a34cadf8f51e@suse.cz> <87k2fpdatl.fsf@tassilo.jf.intel.com> <6f8b1905-818b-bfff-1bf3-5ba04f3b4b64@suse.cz> <20160818155130.GE5871@two.firstfloor.org> <20160818155449.GP14857@tucnak.redhat.com> <5798a459-2fc7-d82a-f89b-30a45a03c831@suse.cz> <8932e842-2457-64a0-76bc-a81b9a9a9b31@suse.cz> <6af6c6fc-9994-ff81-8e07-dab6b647d143@suse.cz> <0dc8a029-696a-39b0-96cc-ab44488607eb@suse.cz> Cc: Jakub Jelinek , Andi Kleen , Jeff Law , Nathan Sidwell , GCC Patches , "Hubicha, Jan" From: =?UTF-8?Q?Martin_Li=c5=a1ka?= Message-ID: Date: Tue, 25 Oct 2016 14:32:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2016-10/txt/msg02026.txt.bz2 On 10/24/2016 03:51 PM, Richard Biener wrote: > It's quite ad-hoc :/ The IFN will also be a memory optimization > barrier unless you add special support > for it in the alias oracle - so the performance measurement needs to > be taken with a grain of salt > (same is true for all atomics of course... - I have some local patches > to improve things here). Good, thus please ping me with the patches you have and I'll integrate it. > > The way you implement process_sm_for_coverage_counter is more like a > final value replacement. > You could maybe use create_iv for the loop counter or even wind up > computing the final value > (number of iterations) only after the loop, avoiding the IV completely > (eventually SCEV cprop > saves you here afterwards). Or maybe we can basically assign loop->niter as the argument of UPDATE_COVERAGE_COUNTER function? Martin > > Richard.