From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 74865 invoked by alias); 27 May 2017 11:16:12 -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 74832 invoked by uid 89); 27 May 2017 11:16:10 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.3 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=act, our X-HELO: mail-vk0-f45.google.com Received: from mail-vk0-f45.google.com (HELO mail-vk0-f45.google.com) (209.85.213.45) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 27 May 2017 11:16:09 +0000 Received: by mail-vk0-f45.google.com with SMTP id y190so15232812vkc.1 for ; Sat, 27 May 2017 04:16:12 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=L5NYBOGPYSRUHG15RI6F6z9JwraAc3Y1Wy7wqiYl9Lk=; b=hYuiQof0hBF6rm6TfQ2zQhk04zWcT9t8T+a9bMZVSc6R4m0u9HTBHGwDKFY7LCTyL/ hhIF1ndOVg4b81ToyKyNeNUJFSp+S39tGT+wu2eaZaaB4DCTW0tnKFAMXDX/BcLaDUir LRMSDmeUkMV1soeBehVn3UZYmPbnWuWEMShYGS4N0VJwnNeTZ/3niK9Ydfs8S2azW3EE aqoST23XH6pd6v7eugGPKNGaqgvjSbXjDavrQixpGi6JzqbVgH+/FROCLZ7n5RH79qx4 woswAZ27k70EIjJOLXICNmLzvZ7zdIjQNOxbL1qBYnBIcfwpMsMFDFU5S4R5ebat1+9H XMZA== X-Gm-Message-State: AODbwcAH+IieXMIY99HEKEuQzlW8ilCp3PIIxPhc2a9ixwd2TPjWb5KN oD7KdTtu10h53T0SG19h+MJ6f9sZBQ== X-Received: by 10.31.57.4 with SMTP id g4mr3157044vka.51.1495883771347; Sat, 27 May 2017 04:16:11 -0700 (PDT) MIME-Version: 1.0 Received: by 10.31.96.201 with HTTP; Sat, 27 May 2017 04:16:10 -0700 (PDT) In-Reply-To: <20170526163053.aj22jelqmoeo7wvd@adacore.com> References: <83poewjb08.fsf@gnu.org> <20170526163053.aj22jelqmoeo7wvd@adacore.com> From: Iain Buclaw Date: Sat, 27 May 2017 11:16:00 -0000 Message-ID: Subject: Re: MinGW compilation warnings in libiberty's waitpid.c To: Joel Brobecker Cc: Eli Zaretskii , DJ Delorie , gcc-patches , GDB Patches Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2017-05/txt/msg00587.txt.bz2 On 26 May 2017 at 18:30, Joel Brobecker wrote: >> 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. > This has been on my todo-list for a little while, as re-syncing is something I normally do after pushing D language support updates into libiberty. However I decided to give it a wait until I got all pending patches in, the last of which I'm just pushing in now. Regards, Iain.