** Description changed: - I was curious and build tested some packages with LTO. So I emptyed lto-disabled-list list, and rebuilt some packages I known in my tests PPA: + I was curious and build tested some packages with LTO. So I emptyed lto-disabled-list list, and rebuilt some packages I known in a test PPA: + https://launchpad.net/~oibaf/+archive/ubuntu/test2/+packages https://launchpad.net/~oibaf/+archive/ubuntu/test/+packages?field.series_filter=resolute - https://launchpad.net/~oibaf/+archive/ubuntu/test2/+packages?field.series_filter=resolute Note: 1) I rebuild the same source package already in resolute after emptying lto-disabled-list 2) only build tested, I didn't test the resulting packages (unless explained) - 3) archs in test PPA, all except amd64v3 - 4) archs in test2 PPA all except armhf, i386 and riscv64 (LTO is never enabled here) + 3) archs in test2 PPA: all except armhf, i386 and riscv64 (LTO is never enabled here) + 4) archs in test PPA: all except amd64v3 source packages removed from ubuntu: llvm-toolchain-9 any - package removed after focal minetest arm64 - package removed after plucky wine-development amd64 arm64 - package removed after jammy LTO builds OK: - 0ad arm64 - note: armhf was broken anyway + 0ad arm64 abiword arm64 assaultcube any - also tested OK on amd64 - note: amd64 binary size of file ac_client is greater with LTO (1834448 vs. 1742288), ac_server is smaller with LTO (524120 vs. 530272) blender s390x compiz any - darkplaces any - 0~20180908~beta1-7 (in sid but still not in resolute) builds fine, see https://launchpad.net/~oibaf/+archive/ubuntu/test2/+packages - dvi2ps any - 5.1j-3 (in sid but still not in resolute) builds fine, see https://launchpad.net/~oibaf/+archive/ubuntu/test2/+packages + darkplaces any + dolphin-emu amd64 arm64 + dvi2ps any + dxvk arm64 + elinks any - reported at: https://github.com/rkd77/elinks/issues/399 - fixed in 0.18.0-2 ezquake any - also (limited) tested OK on amd64 - amd64 binary size of ezquake executable file is smaller with LTO (3723312 vs. 3790704) + glew any hedgewars ppc64el s390x - note: riscv64 and s390x unbuildable due to missing fpc build on s390x since at least xenial imagemagick amd64 + intel-vaapi-driver amd64 pikepdf amd64 retroarch any wine amd64 arm64 - it looks LTO is not used anyway, likely disabled in the package - LTO still (at least partially) broken: - audacious any - it looks like it builds fine but needs updated (removed) symbols - elinks any - fails to build: https://launchpad.net/~oibaf/+archive/ubuntu/test2/+packages - reported at: https://github.com/rkd77/elinks/issues/399 - emacs any - ffmpeg any - actually only amd64 is broken - mame any - at least amd64 is broken - mplayer amd64 - scummvm any - actually only amd64 and arm64 are broken - reported issue at https://bugs.scummvm.org/ticket/16301 + LTO still (at least on some arch) FTBFS: + audacious any - see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015356 + https://github.com/audacious-media-player/audacious/issues/1683 + emacs any - + ffmpeg any - actually only amd64* is broken - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015402 + mame any - build fails with "E: Build killed with signal TERM after 150 minutes of inactivity" + mplayer amd64 - https://trac.mplayerhq.hu/ticket/2408 + scummvm any - actually only amd64* and arm64 are broken - reported issue at https://bugs.scummvm.org/ticket/16301
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2128902 Title: testing lto on some packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lto-disabled-list/+bug/2128902/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
