From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 47618 invoked by alias); 28 Apr 2015 17:14:07 -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 47598 invoked by uid 89); 28 Apr 2015 17:14:06 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Tue, 28 Apr 2015 17:14:05 +0000 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id t3SHE3CR018397 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Tue, 28 Apr 2015 13:14:04 -0400 Received: from localhost.localdomain (ovpn-113-143.phx2.redhat.com [10.3.113.143]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t3SHE3ZT015533; Tue, 28 Apr 2015 13:14:03 -0400 Message-ID: <553FBFDB.4030800@redhat.com> Date: Tue, 28 Apr 2015 17:16:00 -0000 From: Jeff Law User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Caroline Tice , David Edelsohn CC: GCC Patches Subject: Re: [PATCH] Fix size & type for cold partition names (hot-cold function partitioning) References: In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2015-04/txt/msg01773.txt.bz2 On 04/28/2015 11:12 AM, Caroline Tice wrote: > Yes, this is already mentioned in PR 65910 > (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65910). > > There is a patch mentioned in that PR that both appears to fix the > problem and appears to have been approved. I thought the author of > the patch would commit it, but that does not appear to have happened > yet. Should I go ahead and commit that patch, or should I wait for > the author to do that? If it's not committed, go ahead and do so. jeff