On 06.05.2018 16:48, Vadim Zeitlin wrote: > On Sun, 6 May 2018 13:42:48 +0200 Matthias Klose <d...@debian.org> wrote: > > MK> I am not aware of any Debian local patches which could trigger that. > Please > MK> could you check if you can reproduce this with GCC 8 as well? > > I can't reproduce the problem with the minimized test case using gcc 8 > from Sid (8.1.0-1). As an aside, gcc 8 also produces much smaller (less > than 50%) assembly and object code from the same files compared to gcc 7, > which surprised me. FWIW I can still reproduce the problem with the > latest g++-7 (7.3.0-17) in exactly the same way as originally reported for > 7.2. > > The original problem, in the real program I was working on, only appeared > when using MinGW, so I can't [easily] test whether it is still present or > not as there is no gcc-mingw-w64 8 in Debian yet, but I'll do it when it > becomes available.
I doubt I'll have time for this. If you know how to build a debian package, you could have a look at the gcc-7 package, debian/rules.patch and try to disable some patches (is a gcc upstream snapshot taken from the gcc-7-branch ok?), and then see if things get better. svn-updates is the big hammer, but you could try to disable libstdc++-pic to pr84761 and see if things get better. Matthias
