On Mon, Apr 18, 2016 at 12:31 PM, Peter Eisentraut <peter_e@gmx.net> wrote:
> I don't know if it's worth tracking this as an open item and thus
> kind-of release blocker if no one else has the problem. But I
> definitely still have it. My initial suspicion was that this had
> something to do with a partial upgrade to gcc 6 (not yet released), in
> other words a messed up system. But I was able to reproduce it in a
> freshly installed chroot. It only happens with various versions of gcc,
> but not with clang. So I'm going to have to keep digging.
gcc is moving slowly but surely to have 6.0 in a released state btw:
https://gcc.gnu.org/ml/gcc/2016-04/msg00103.html
--
Michael
