On 26 May 2017 at 18:30, Joel Brobecker <brobec...@adacore.com> 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.