On 12 September 2017 at 23:58, Dave Gittins wrote:
> I confirmed this issue on x86_64 CentOS, and independently here:
> https://wandbox.org/permlink/ncWqA9Zu3YEofqri
>
> Also fails on gcc trunk.
>
> Possibly related to bug 81338 "stringstream remains empty after being
> moved into multiple times"?
I confirmed this issue on x86_64 CentOS, and independently here:
https://wandbox.org/permlink/ncWqA9Zu3YEofqri
Also fails on gcc trunk.
Possibly related to bug 81338 "stringstream remains empty after being
moved into multiple times"? Although I see that one is fixed by Mr
Wakely.
Dave
On Tue,
Hi,
Apologies if I am coming about this in the wrong way, I am new to the
mailing list. During our preliminary work to upgrade to gcc 7.2 (from
6.3) at my workplace, we have come across a bug that is blocking our
move to C++17. I have raised a bug report here:
https://gcc.gnu.org/bugzilla/show_bug