From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22418 invoked by alias); 30 Jul 2013 19:48:59 -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 22408 invoked by uid 89); 30 Jul 2013 19:48:59 -0000 X-Spam-SWARE-Status: No, score=-3.1 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,RDNS_NONE,SPF_PASS autolearn=ham version=3.3.1 Received: from Unknown (HELO mail-ob0-f170.google.com) (209.85.214.170) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Tue, 30 Jul 2013 19:48:58 +0000 Received: by mail-ob0-f170.google.com with SMTP id eh20so1146634obb.1 for ; Tue, 30 Jul 2013 12:48:50 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=feYhJF1wX9yDCzxvOEDGrlJNKTm3bI3f+PqiRNlE9Bg=; b=RZPYYU7vGGG1WUrbPljCYRpDowcs8l0tfSYFmCo3UAGXNDjIX6djrkxtdJDs9EGS4Y Ox+8tRrf5XnLaPB4FfRRtERa/oQJMhJ1H0Qq5noMggrQDTTkHYUkHbst/Ye2qb2F05wH ublFtqd7xslZk4SI6VT17rPqZQ1kaARrf6y29KQi3e8wTJ3QzR9+CPwJo3qvEbMrlduA jsCqEqpWZpmVZVmmcpYbAi7hF4iDsfg0nHFWYPmKu7cSZSGrJqijdMBce9iYf9sKGAMv 6THMgjllGBvWMOSplxeXJYfCFJpEqSVpflXOk+ysbzIciRThR/StuMXnFXoaWTs5xOS/ Jupg== MIME-Version: 1.0 X-Received: by 10.182.220.130 with SMTP id pw2mr57761797obc.80.1375213730549; Tue, 30 Jul 2013 12:48:50 -0700 (PDT) Received: by 10.182.213.74 with HTTP; Tue, 30 Jul 2013 12:48:50 -0700 (PDT) In-Reply-To: References: Date: Tue, 30 Jul 2013 19:50:00 -0000 Message-ID: Subject: Re: [Google] Fix profiledbootstrap failure From: Rong Xu To: Xinliang David Li Cc: Teresa Johnson , Dinar Temirbulatov , GCC Patches Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQmtSOtni7EGuw2SIOrsLRP+yc8U5fAuWZawM9rnHa9AI7MO6p4Rr7kMxmkHkPnH6YcX8J0TtMxp36vMYHxXkn+7kE1cKkK+nrlWkcwPvgkKh+JcDShcKOMDH8m0bAudCPe4bTCKdhVjOKJuyIdPjsRb4QFpXWccZkKOKZPc009437z+FQSWn7v9J3V6aRDbUSqH/150QNl+++wqhMESYF7mSZpfZQ== X-SW-Source: 2013-07/txt/msg01504.txt.bz2 We have seen the issue before. It does fail the profile boostrap as it reads a wrong gcda file. I thought it had been fixed. (The fix was as David mentioned, setting the default value of the parameter to 0). -Rong On Tue, Jul 30, 2013 at 12:02 PM, Xinliang David Li wrote: > I need to understand why this affects profile bootstrap -- is this due > to file name conflict? > > The fix is wrong -- please do not remove the parameter. If it is a > problem, a better fix is to change the default parameter value to 0. > > David > > > On Tue, Jul 30, 2013 at 11:56 AM, Teresa Johnson wrote: >> cc'ing Rong and David since this came from LIPO support. >> >> The patch as-is removes the one use of PARAM_GCOV_DEBUG (which is on >> by default) without removing the parameter itself. What is the failure >> mode you see from this code? >> >> Thanks, >> Teresa >> >> On Tue, Jul 30, 2013 at 11:50 AM, Dinar Temirbulatov >> wrote: >>> Hello >>> >>> This change allows to complete profiledbootstrap on the google gcc-4.8 >>> branch, tested with make bootstrap with no new regressions. OK for >>> google 4.8? >>> thanks, Dinar. >> >> >> >> -- >> Teresa Johnson | Software Engineer | tejohnson@google.com | 408-460-2413