Well, thats great! Thanks mlau for the info!

This correction should come with the recent release of gcc 7.3, so this issue may disappear...