https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65810
Bug ID: 65810 Summary: powerpc64 libgfortran alignment issue? Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: amodra at gmail dot com Testsuite results between two identical powerpc64-linux builds, except for the source path name, differ. +FAIL: gfortran.dg/fmt_en.f90 -O0 execution test +FAIL: gfortran.dg/fmt_en.f90 -O0 scan-file All kinds rounded to nearest +FAIL: gfortran.dg/fmt_en.f90 -O1 execution test +FAIL: gfortran.dg/fmt_en.f90 -O1 scan-file All kinds rounded to nearest +FAIL: gfortran.dg/fmt_en.f90 -O2 execution test +FAIL: gfortran.dg/fmt_en.f90 -O2 scan-file All kinds rounded to nearest +FAIL: gfortran.dg/fmt_en.f90 -O3 -fomit-frame-pointer execution test +FAIL: gfortran.dg/fmt_en.f90 -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions execution test +FAIL: gfortran.dg/fmt_en.f90 -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions scan-file All kinds rounded to nearest +FAIL: gfortran.dg/fmt_en.f90 -O3 -fomit-frame-pointer -funroll-loops execution test +FAIL: gfortran.dg/fmt_en.f90 -O3 -fomit-frame-pointer -funroll-loops scan-file All kinds rounded to nearest +FAIL: gfortran.dg/fmt_en.f90 -O3 -fomit-frame-pointer scan-file All kinds rounded to nearest +FAIL: gfortran.dg/fmt_en.f90 -O3 -g execution test +FAIL: gfortran.dg/fmt_en.f90 -O3 -g scan-file All kinds rounded to nearest +FAIL: gfortran.dg/fmt_en.f90 -Os execution test +FAIL: gfortran.dg/fmt_en.f90 -Os scan-file All kinds rounded to nearest +FAIL: gfortran.dg/large_real_kind_1.f90 -O0 execution test +FAIL: gfortran.dg/large_real_kind_1.f90 -O1 execution test +FAIL: gfortran.dg/large_real_kind_1.f90 -O2 execution test +FAIL: gfortran.dg/large_real_kind_1.f90 -O3 -fomit-frame-pointer execution test +FAIL: gfortran.dg/large_real_kind_1.f90 -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions execution test +FAIL: gfortran.dg/large_real_kind_1.f90 -O3 -fomit-frame-pointer -funroll-loops execution test +FAIL: gfortran.dg/large_real_kind_1.f90 -O3 -g execution test +FAIL: gfortran.dg/large_real_kind_1.f90 -Os execution test +FAIL: gfortran.dg/quad_2.f90 -O0 execution test +FAIL: gfortran.dg/quad_2.f90 -O1 execution test +FAIL: gfortran.dg/quad_2.f90 -O2 execution test +FAIL: gfortran.dg/quad_2.f90 -O3 -fomit-frame-pointer execution test +FAIL: gfortran.dg/quad_2.f90 -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions execution test +FAIL: gfortran.dg/quad_2.f90 -O3 -fomit-frame-pointer -funroll-loops execution test +FAIL: gfortran.dg/quad_2.f90 -O3 -g execution test +FAIL: gfortran.dg/quad_2.f90 -Os execution test Both compilers configured with CC="gcc -m64" CXX="g++ -m64" \ ${gcc_src}/configure --build=powerpc64-linux \ --with-cpu=power7 \ --disable-nls --enable-__cxa_atexit --enable-secureplt \ --with-long-double-128 --enable-gnu-indirect-function \ --enable-languages=all,go --enable-lto In one case gcc_src=/home/amodra/src/gcc-5-virgin the other gcc_src=/home/amodra/src/gcc-5-vir Running the testcases by hand with different LD_LIBRARY_PATH show the problem is in libgfortran, not the testcase code. valgrind doesn't show any uninitialized accesses. Looking at quad_2.f90 under gdb, I see the abort is due to str3 having an extra leading space.