From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5456 invoked by alias); 30 Jul 2013 19:58: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 5430 invoked by uid 89); 30 Jul 2013 19:58:59 -0000 X-Spam-SWARE-Status: No, score=-3.7 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-wi0-f172.google.com) (209.85.212.172) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Tue, 30 Jul 2013 19:58:58 +0000 Received: by mail-wi0-f172.google.com with SMTP id hj13so2581307wib.17 for ; Tue, 30 Jul 2013 12:58: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=Gk24sX0QI8BcOWCqw19cUI6PNkoENu1r09rTHyP1Pko=; b=XQprLcsIJXfadsRJ/ZufmbL/fVc480mpy2sufBPeKZiu4HBHqsBjrqPQ1egSm9Bo3k I5nDPs4v0rGwp3sdlr+EpLD7cSlAFnNmBSFx90QRhXFNiZKqkwbciBaPYvkBp/eIea78 COrKy4x2zgyGQi2EKv+Iy+KyLiy32jhr3E02HxcEZoyFZe06dC56W0W134tSvBa/gMmC +bZGLzOK9N+A0QIO8RIDFOpO56gGDiOioa6C1gvir/EJ3WfRJE5UeqN52BcPDSOCchdI g5PuZIfgF14U/f/9dqBzlgWmwKJkfvDTh8RWdhMXU2i0HogshrTaFI0Yr0nT5xJQOaLL MjDg== MIME-Version: 1.0 X-Received: by 10.194.243.101 with SMTP id wx5mr47351223wjc.49.1375214330069; Tue, 30 Jul 2013 12:58:50 -0700 (PDT) Received: by 10.180.91.82 with HTTP; Tue, 30 Jul 2013 12:58:49 -0700 (PDT) In-Reply-To: References: Date: Tue, 30 Jul 2013 20:01:00 -0000 Message-ID: Subject: Re: [Google] Fix profiledbootstrap failure From: Xinliang David Li To: Rong Xu Cc: Teresa Johnson , Dinar Temirbulatov , GCC Patches Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQmLnoQ858vS9HNrQygtn6U6XrBbBV86BTYhgvmPR/pj1m4PBAaN2+L5vNujbQ5JttnLCHkrY0OMcHWlcVa3L0F55985z/5sbhA9BvNc89bPc9Vau0dkXo8XpBPJ1RwaM5T3QZ5azxetTq5b2TDwUHGHgtqsj+VS9M6cnorFYPVEVB7D+zfgovf5+FyS9SWo4KiAfviHGmlxaNp4n+V7ETOlbS0zYw== X-SW-Source: 2013-07/txt/msg01506.txt.bz2 Ok. Rong, can you help commit the parameter default setting patch? thanks, David On Tue, Jul 30, 2013 at 12:48 PM, Rong Xu wrote: > 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