From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 101167 invoked by alias); 20 Apr 2015 00:10:34 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 101128 invoked by uid 48); 20 Apr 2015 00:10:30 -0000 From: "amodra at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/65810] New: powerpc64 libgfortran alignment issue? Date: Mon, 20 Apr 2015 00:10:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: amodra at gmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-04/txt/msg01569.txt.bz2 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.