http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50906
--- Comment #18 from Kyle Moffett <Kyle.D.Moffett at boeing dot com> 2011-11-28 19:30:07 UTC --- I am happy to report that your updated 4.6.2 patch seems to be 100% functional on e500/SPE. I get identical "test-summary" reports for patched-4.6.2 with and without BOOT_CFLAGS="-g -Os", apart from the different build directory paths (EG: /srv/build/gcc-4.6-normal versus /srv/build/gcc-4.6-Os), As before, the following testsuite failures are fixed relative to unpatched 4.6.2: -FAIL: g++.dg/torture/stackalign/eh-vararg-1.C -Os execution test -FAIL: g++.dg/torture/stackalign/eh-vararg-2.C -Os execution test -FAIL: g++.dg/torture/stackalign/eh-vararg-1.C -Os execution test -FAIL: g++.dg/torture/stackalign/eh-vararg-2.C -Os execution test And again, as before, the following 64-bit-only tests are erroneously run on 32-bit e500 CPUs, although they were inexplicably successful during a previous build. +FAIL: gcc.target/powerpc/ppc-fma-5.c execution test +FAIL: gfortran.dg/pr47614.f -O0 execution test +FAIL: gfortran.dg/pr47614.f -O1 execution test +FAIL: gfortran.dg/pr47614.f -O2 execution test +FAIL: gfortran.dg/pr47614.f -O3 -fomit-frame-pointer execution test +FAIL: gfortran.dg/pr47614.f -O3 -fomit-frame-pointer -funroll-loops +FAIL: gfortran.dg/pr47614.f -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions execution test +FAIL: gfortran.dg/pr47614.f -O3 -g execution test +FAIL: gfortran.dg/pr47614.f -Os execution test Thanks again for your help! Cheers, Kyle Moffett
