On Fri, Dec 09, 2016 at 01:01:01AM +0100, gregor herrmann wrote: > On Fri, 09 Dec 2016 01:14:23 +0200, Niko Tyni wrote: > > > TL;dr: this is https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78176 > > Oh. > > > > > Otherwise a backtrace for a -g build from the crash would be handy: > > > > perl Makefile.PL OPTIMIZE=-g > > It goes away without the default optimization level -O2. > > > > On eller.debian.org, mipsel chroot, with OPTIMIZE="-g -O2": > [..] > > I think a want to book a workshop "gdb for harmless perl packagers" > :) > > > Unfortunately gcc doesn't seem to have a targeted option to disable this > > optimization. Building with -O0 on mips and mipsel is probably the best > > workaround we have (-O1 isn't enough.) > > I now cam up with the following change to d/rules: > > +# #847397 > +DEB_HOST_ARCH = $(shell dpkg-architecture -qDEB_HOST_ARCH) > +NOOPT = mips mipsel amd64 > +ifneq (,$(filter $(DEB_HOST_ARCH), $(NOOPT))) > +export DEB_CFLAGS_MAINT_STRIP:=-O2 > +export DEB_CFLAGS_MAINT_APPEND:=-O0 > +endif > > (committed and pushed). Does this make sense (if I remove the > debugging amd64 again, or course)? >
That certainly looks like a sensible workaround. Is there some mechanism that will remove it if the gcc (or perhaps kernel) bug is fixed? Tony