On Tue, Jan 02, 2018 at 01:49:06PM +0100, Helmut Grohne wrote: > On Tue, Jan 02, 2018 at 10:57:44AM +0100, Mark Wielaard wrote: > > Could you please file a bug for that. I am not aware of any such issue. > > So would like to fix it, and would if I knew about it. Thanks. > > No. Matthias Klose will file them, when he considers gcc-8 ready as some > of the gcc-8 issues are indeed compiler bugs.
That is good. I know Matthias and he does indeed report issues like these upstream early and often. > Reporting this issue again is useless as > you'd have to wade through the report again figuring that it already is > fixed and turn it into a "new upstream release please"-bug. Don't worry too much about duplicates. You can just file it against the debian bugtracker. I am happy to provide patches, and it is good to know which distro is using which gcc/binutils release. > In contrast, what we need is that essential is buildable roughly 90% of > the time. That means you get roughly 3 days for fixing, not 3 months. In > Debian, not upstream. This is a hard requirement or we can just stop > doing QA as it would become infeasible. In general, if it is a new gcc release, we will likely have seen the issue before upstream or in another distro and can providing a patch to include in the debian package can normally be done in 3 days. This is what we do with other distros too. > We can try using jenkins.d.n resources. There I'm cross building > elfutils for alpha, arm64, armel, armhf, i386, kfreebsd-i386, m68k, > mips64el, mips, mipsel, nios2, powerpc, powerpcspe, ppc64, ppc64el, > s390x, sh4, sparc, sparc64, tilegx, x32 and would like to cross build it > for some more (including musl-linux-any, mips64r6el, ia64, sh3, hppa). That would be nice. Note that some of those setups (particular the mips variants) don't have upstream support yet. It would be nice to get the Debian backend patches upstreamed before we add some of those to the CI. > Compare to glibc maybe. glibc relates very closely to gcc, so it > declares which compiler versions are "supported". elfutils is a bit like glibc indeed. It gets tested against the latest stable gcc and binutils releases in the various distros (at least those in debian, fedora, centos through the CI) and if gcc is in stage1 then the next version will most likely also have been checked already. When tested a new arch/toolchain please involve upstream as soon as possible. We really are interested. And would like to have warning free and zero-fail builds for all distros. Cheers, Mark
