reopen 746426 reassign 746426 gcc-8 thanks On Wed, Jan 23, 2019 at 03:32:32PM +0100, Mark Wielaard wrote: > Hi Kurt, > > I saw Debian Bug#746426 was recently closed. > You originally wrote: > > > It seems that not all arches have -fasynchronous-unwind-tables > > enabled. I see it enabled on amd64, i386, s390x, but disabled > > on armel/armhf, powerpc. > > > > Could this enable this on more architectures? > > > > I'm currently seeing elfutils test failures on powerpc because > > the unwind information is not available. I'll probably also get > > this problem on arm64 if it's not enabled there. > > I agree that enabling -fasynchronous-unwind-tables is a good thing in > general. It is what Fedora does for example. Without precise unwind > tables you need some fallback unwinder which has to guess at how call > frames work and won't be reliable. > > Is there a way to clone/reopen this bug against a newer Debian gcc > release?
I've reassign it to gcc-8 now. I can also clone it to gcc-9 if needed. > In theory the fallback unwinders in elfutils should be good enough to > make the testsuite PASS. But they might not. Are you still seeing > unwinding/backtrace related failures? On which platforms? I see the tests getting skipped on most arches, because unwinding is not supported. These work: amd64, x32 These have at least 1 test that says unwinding is not supported: arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x, alpha, hppa, ia64, powerpc, ppc64el, riscv64, sparc64 But those pass at least run-backtrace-native: arm64, armel, armhf, i386, ppc64el, s390x, powerpc, ppc64, sparc64 This means that for the arches we release for, mips* is the only one that does not pass run-backtrace-native. Unknown: powerpcspe, m68k, sh4 Kurt
