public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amodra at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/65810] New: powerpc64 libgfortran alignment issue? Date: Mon, 20 Apr 2015 00:10:00 -0000 [thread overview] Message-ID: <bug-65810-4@http.gcc.gnu.org/bugzilla/> (raw) 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.
next reply other threads:[~2015-04-20 0:10 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-04-20 0:10 amodra at gmail dot com [this message] 2015-04-20 1:43 ` [Bug target/65810] " jvdelisle at gcc dot gnu.org 2015-04-20 2:15 ` bergner at gcc dot gnu.org 2015-04-20 3:14 ` amodra at gmail dot com 2015-04-20 5:24 ` amodra at gmail dot com 2015-04-20 9:45 ` [Bug target/65810] powerpc64 alignment of r2 insufficient for loading long-double constants dominiq at lps dot ens.fr 2015-04-20 13:14 ` amodra at gmail dot com 2015-04-28 3:48 ` amodra at gcc dot gnu.org 2015-04-28 3:50 ` amodra at gmail dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-65810-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).