https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77821
--- Comment #7 from PeteVine <tulipawn at gmail dot com> --- The bug doesn't occur on an aarch64 system (built with gcc5): $ du ufo-arm64-gcc* 3312 ufo-arm64-gcc5 3072 ufo-arm64-gcc5-lto 3256 ufo-arm64-gcc6 3056 ufo-arm64-gcc6-lto 3288 ufo-arm64-gcc7 3040 ufo-arm64-gcc7-lto This could mean the issue revolves around C++ gcc4 ABI and libraries built with different libstdc++/gcc versions. Does that sound plausible? (everything works perfectly fine at runtime and there must be a reason the problem starts occurring at gcc5 boundary) The previous comment might be completely tangential to this issue.
