From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20700 invoked by alias); 26 May 2017 16:30:56 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 19573 invoked by uid 89); 26 May 2017 16:30:55 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=occasional, H*Ad:U*dj, act, our X-HELO: rock.gnat.com Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 26 May 2017 16:30:53 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id B0C7FF3EE1; Fri, 26 May 2017 12:30:55 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 5HdC2H5aquq1; Fri, 26 May 2017 12:30:55 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 7C766F3E81; Fri, 26 May 2017 12:30:55 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id BA1A58039E; Fri, 26 May 2017 09:30:53 -0700 (PDT) Date: Fri, 26 May 2017 16:30:00 -0000 From: Joel Brobecker To: Eli Zaretskii Cc: DJ Delorie , gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org Subject: Re: MinGW compilation warnings in libiberty's waitpid.c Message-ID: <20170526163053.aj22jelqmoeo7wvd@adacore.com> References: <83poewjb08.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <83poewjb08.fsf@gnu.org> User-Agent: NeoMutt/20170113 (1.7.2) X-SW-Source: 2017-05/txt/msg00569.txt.bz2 > Thanks. Is the environ thing also fixed? > > Joel/Pedro, how should I go about making sure these changes are in the > GDB copy of libiberty? Normally, I'd expect someone pushing to GCC's libibert to also update our repo accordingly. However, it's easy to forget so, if you notice a change that was not propagated to us, we just cherry-pick those changes so as to make sure our copy is up to date with GCC's. We also see the occasional "resync libiberty" commits which act as a failsafe, but I don't think we should wait for one of those. Should those ones be pushed to the gdb-8.0-branch as well? -- Joel