** Description changed: + [SRU Justification] gcc-5 from Ubuntu is configured with MPX support, but it is broken due - to always-added linker option "-as-needed". + to always-added linker option "-as-needed". + + [Test case] + 1. Pass -mmpx to gcc when building an arbitrary project on x86. + 2. Verify with ldd that the resulting executable is not linked against libmpx.so because the -as-needed flag has discarded the mpx library from being linked in. + 3. Install binutils and gcc-5 from -proposed. + 4. Rebuild the target, again with -mmpx. + 5. Verify with ldd that the new executable is linked against libmpx.so. + 6. Verify that there are no regressions in the binutils testsuite on any architectures, by manually checking the results in the build log. + + [Regression potential] + This binutils patch implements new --push-state / --pop-state options which will not be used in the common case, only when -mmpx is passed. When these flags are not in use, which is the default, it should have no effect on the behavior of the toolchain, so risk of regression is minimal. + Here is the GCC upstream bug & fix https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77267 https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=240057 Would it be possible to backport this fix to Ubuntu gcc-5 build?
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1623418 Title: gcc-as-needed.diff patch broke mpx support in GCC Status in gcc: Unknown Status in binutils package in Ubuntu: Fix Released Status in gcc-5 package in Ubuntu: New Status in gcc-6 package in Ubuntu: Fix Released Status in binutils source package in Xenial: New Status in gcc-5 source package in Xenial: New Bug description: [SRU Justification] gcc-5 from Ubuntu is configured with MPX support, but it is broken due to always-added linker option "-as-needed". [Test case] 1. Pass -mmpx to gcc when building an arbitrary project on x86. 2. Verify with ldd that the resulting executable is not linked against libmpx.so because the -as-needed flag has discarded the mpx library from being linked in. 3. Install binutils and gcc-5 from -proposed. 4. Rebuild the target, again with -mmpx. 5. Verify with ldd that the new executable is linked against libmpx.so. 6. Verify that there are no regressions in the binutils testsuite on any architectures, by manually checking the results in the build log. [Regression potential] This binutils patch implements new --push-state / --pop-state options which will not be used in the common case, only when -mmpx is passed. When these flags are not in use, which is the default, it should have no effect on the behavior of the toolchain, so risk of regression is minimal. Here is the GCC upstream bug & fix https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77267 https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=240057 Would it be possible to backport this fix to Ubuntu gcc-5 build? To manage notifications about this bug go to: https://bugs.launchpad.net/gcc/+bug/1623418/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
