Hello bugproxy, or anyone else affected, Accepted gcc-4.8 into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gcc-4.8/4.8.4-2ubuntu1~14.04 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: gcc-4.8 (Ubuntu Trusty) Status: New => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu. https://bugs.launchpad.net/bugs/1437467 Title: gcc 4.8: Wrong code for vector doubleword extract Status in gcc-4.8 package in Ubuntu: Fix Released Status in gcc-4.8 source package in Trusty: Fix Committed Status in gcc-4.8 source package in Vivid: Fix Released Bug description: ---Problem Description--- GCC 4.8 produces wrong code for powerpc64le-*-* when extracting the second doubleword of a V2DF or V2DI vector from memory. This has been fixed upstream as revision r221696. The revised test gcc/testsuite/gcc.dg/vmx/extract-vsx.c can be used to verify the problem on an unfixed compiler, and to verify the solution on a fixed one. Machine Type = POWER8 ---Steps to Reproduce--- Compile and run the revised gcc/testsuite/gcc.dg/vmx/extract-vsx.c found in the patch, according to the steps in the test case. This bug occurs only in GCC 4.8, so if I understand correctly this only affects the 14.04 LTS release. I would like to request that this patch be applied in the next point release for 14.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1437467/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
