This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: MinGW compilation warnings in libiberty's waitpid.c
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Joel Brobecker <brobecker at adacore dot com>
- Cc: dj at redhat dot com, gcc-patches at gcc dot gnu dot org, gdb-patches at sourceware dot org
- Date: Fri, 26 May 2017 20:42:52 +0300
- Subject: Re: MinGW compilation warnings in libiberty's waitpid.c
- Authentication-results: sourceware.org; auth=none
- References: <xnpoeyey3z.fsf@greed.delorie.com> <83poewjb08.fsf@gnu.org> <20170526163053.aj22jelqmoeo7wvd@adacore.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Fri, 26 May 2017 09:30:53 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: DJ Delorie <dj@redhat.com>, gcc-patches@gcc.gnu.org,
> gdb-patches@sourceware.org
>
> 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.
What can I do to expedite the process? This currently holds the 8.0
release, and I'm uneasy to be the culprit.
> Should those ones be pushed to the gdb-8.0-branch as well?
Yes.