Re: libstdc++ bootstrap failure after r261525

2018-06-13 Thread François Dumont
Here is the missing part of the can_advance patch.     * include/debug/helper_functions.h     (__gnu_debug::_Safe_iterator<>): Add declaration.     (__can_advance(_Ite, _Size)): New.     (__can_advance(const _Safe_iterator<>&, _Size)): Overload declaration.     * include/debug/functions.h     (__

Re: libstdc++ bootstrap failure after r261525

2018-06-13 Thread François Dumont
I pick up the wrong "can_advance" patch. I should have taken another one first. So I'll send and apply the missing one providing the debug __can_advance in a couple of hours. Sorry On 13/06/2018 15:24, Jonathan Wakely wrote: On 13/06/18 13:42 +0200, Paolo Carlini wrote: Hi, On 13/06/2018

Re: libstdc++ bootstrap failure after r261525

2018-06-13 Thread Jonathan Wakely
On 13/06/18 13:42 +0200, Paolo Carlini wrote: Hi, On 13/06/2018 08:11, François Dumont wrote: On 12/06/2018 23:26, Martin Sebor wrote: Bootstrap fails in libstdc++ with the following error. I haven't investigated it much except to take a peek at recent libstdc++ commits where r261525 looks lik

Re: libstdc++ bootstrap failure after r261525

2018-06-13 Thread Paolo Carlini
Hi, On 13/06/2018 08:11, François Dumont wrote: On 12/06/2018 23:26, Martin Sebor wrote: Bootstrap fails in libstdc++ with the following error. I haven't investigated it much except to take a peek at recent libstdc++ commits where r261525 looks like it introduced __glibcxx_check_can_increment_r

Re: libstdc++ bootstrap failure after r261525

2018-06-12 Thread François Dumont
On 12/06/2018 23:26, Martin Sebor wrote: Bootstrap fails in libstdc++ with the following error. I haven't investigated it much except to take a peek at recent libstdc++ commits where r261525 looks like it introduced __glibcxx_check_can_increment_range, so it seems like it might have something to

Re: libstdc++ bootstrap failure after r261525

2018-06-12 Thread Jeff Law
On 06/12/2018 03:26 PM, Martin Sebor wrote: > Bootstrap fails in libstdc++ with the following error. > I haven't investigated it much except to take a peek > at recent libstdc++ commits where r261525 looks like it > introduced __glibcxx_check_can_increment_range, so it > seems like it might have so