public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/96983] New: [11 regression] ICE compiling gfortran.dg/pr96711.f90 starting with r11-3042 Date: Tue, 08 Sep 2020 13:21:31 +0000 [thread overview] Message-ID: <bug-96983-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96983 Bug ID: 96983 Summary: [11 regression] ICE compiling gfortran.dg/pr96711.f90 starting with r11-3042 Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: seurer at gcc dot gnu.org Target Milestone: --- g:9164caf25cb210ad0a69357b226e39913aff00d1, r11-3042 make -k check-gcc-fortran RUNTESTFLAGS="dg.exp=gfortran.dg/pr96711.f90" FAIL: gfortran.dg/pr96711.f90 -O0 (internal compiler error) FAIL: gfortran.dg/pr96711.f90 -O0 (test for excess errors) FAIL: gfortran.dg/pr96711.f90 -O1 (internal compiler error) FAIL: gfortran.dg/pr96711.f90 -O1 (test for excess errors) FAIL: gfortran.dg/pr96711.f90 -O2 (internal compiler error) FAIL: gfortran.dg/pr96711.f90 -O2 (test for excess errors) FAIL: gfortran.dg/pr96711.f90 -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions (internal compiler error) FAIL: gfortran.dg/pr96711.f90 -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions (test for excess errors) FAIL: gfortran.dg/pr96711.f90 -O3 -g (internal compiler error) FAIL: gfortran.dg/pr96711.f90 -O3 -g (test for excess errors) FAIL: gfortran.dg/pr96711.f90 -Os (internal compiler error) FAIL: gfortran.dg/pr96711.f90 -Os (test for excess errors) # of unexpected failures 12 # of unresolved testcases 12 Executing on host: /home/seurer/gcc/git/build/gcc-test/gcc/testsuite/gfortran/../../gfortran -B/home/seurer/gcc/git/build/gcc-test/gcc/testsuite/gfortran/../../ -B/home/seurer/gcc/git/build/gcc-test/powerpc64le-unknown-linux-gnu/./libgfortran/ /home/seurer/gcc/git/gcc-test/gcc/testsuite/gfortran.dg/pr96711.f90 -fdiagnostics-plain-output -fdiagnostics-plain-output -O3 -g -pedantic-errors -fdump-tree-original -B/home/seurer/gcc/git/build/gcc-test/powerpc64le-unknown-linux-gnu/./libgfortran/.libs -L/home/seurer/gcc/git/build/gcc-test/powerpc64le-unknown-linux-gnu/./libgfortran/.libs -L/home/seurer/gcc/git/build/gcc-test/powerpc64le-unknown-linux-gnu/./libgfortran/.libs -L/home/seurer/gcc/git/build/gcc-test/powerpc64le-unknown-linux-gnu/./libatomic/.libs -B/home/seurer/gcc/git/build/gcc-test/powerpc64le-unknown-linux-gnu/./libquadmath/.libs -L/home/seurer/gcc/git/build/gcc-test/powerpc64le-unknown-linux-gnu/./libquadmath/.libs -L/home/seurer/gcc/git/build/gcc-test/powerpc64le-unknown-linux-gnu/./libquadmath/.libs -lm -o ./pr96711.exe (timeout = 300) spawn -ignore SIGHUP /home/seurer/gcc/git/build/gcc-test/gcc/testsuite/gfortran/../../gfortran -B/home/seurer/gcc/git/build/gcc-test/gcc/testsuite/gfortran/../../ -B/home/seurer/gcc/git/build/gcc-test/powerpc64le-unknown-linux-gnu/./libgfortran/ /home/seurer/gcc/git/gcc-test/gcc/testsuite/gfortran.dg/pr96711.f90 -fdiagnostics-plain-output -fdiagnostics-plain-output -O3 -g -pedantic-errors -fdump-tree-original -B/home/seurer/gcc/git/build/gcc-test/powerpc64le-unknown-linux-gnu/./libgfortran/.libs -L/home/seurer/gcc/git/build/gcc-test/powerpc64le-unknown-linux-gnu/./libgfortran/.libs -L/home/seurer/gcc/git/build/gcc-test/powerpc64le-unknown-linux-gnu/./libgfortran/.libs -L/home/seurer/gcc/git/build/gcc-test/powerpc64le-unknown-linux-gnu/./libatomic/.libs -B/home/seurer/gcc/git/build/gcc-test/powerpc64le-unknown-linux-gnu/./libquadmath/.libs -L/home/seurer/gcc/git/build/gcc-test/powerpc64le-unknown-linux-gnu/./libquadmath/.libs -L/home/seurer/gcc/git/build/gcc-test/powerpc64le-unknown-linux-gnu/./libquadmath/.libs -lm -o ./pr96711.exe f951: internal compiler error: Could not find real kind with at least 128 bits 0x102465e3 gfc_report_diagnostic /home/seurer/gcc/git/gcc-test/gcc/fortran/error.c:782 0x10248643 gfc_internal_error(char const*, ...) /home/seurer/gcc/git/gcc-test/gcc/fortran/error.c:1402 0x103d1dc7 build_round_expr /home/seurer/gcc/git/gcc-test/gcc/fortran/trans-intrinsic.c:406 0x103d1dc7 build_fix_expr /home/seurer/gcc/git/gcc-test/gcc/fortran/trans-intrinsic.c:436 0x103d2023 gfc_conv_intrinsic_int /home/seurer/gcc/git/gcc-test/gcc/fortran/trans-intrinsic.c:566 0x103e35d3 gfc_conv_intrinsic_function(gfc_se*, gfc_expr*) /home/seurer/gcc/git/gcc-test/gcc/fortran/trans-intrinsic.c:10171 0x103a52cb gfc_conv_function_expr /home/seurer/gcc/git/gcc-test/gcc/fortran/trans-expr.c:7547 0x103b551f gfc_trans_assignment_1 /home/seurer/gcc/git/gcc-test/gcc/fortran/trans-expr.c:10903 0x10347467 trans_code /home/seurer/gcc/git/gcc-test/gcc/fortran/trans.c:1864 0x103905b3 gfc_generate_function_code(gfc_namespace*) /home/seurer/gcc/git/gcc-test/gcc/fortran/trans-decl.c:6865 0x1034df63 gfc_generate_code(gfc_namespace*) /home/seurer/gcc/git/gcc-test/gcc/fortran/trans.c:2214 0x102d34ab translate_all_program_units /home/seurer/gcc/git/gcc-test/gcc/fortran/parse.c:6347 0x102d34ab gfc_parse_file() /home/seurer/gcc/git/gcc-test/gcc/fortran/parse.c:6616 0x10342d4b gfc_be_parse_file /home/seurer/gcc/git/gcc-test/gcc/fortran/f95-lang.c:212
next reply other threads:[~2020-09-08 13:21 UTC|newest] Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-08 13:21 seurer at gcc dot gnu.org [this message] 2020-09-08 14:18 ` [Bug fortran/96983] " anlauf at gcc dot gnu.org 2020-09-08 14:21 ` rguenth at gcc dot gnu.org 2020-09-08 15:50 ` anlauf at gcc dot gnu.org 2020-09-08 19:08 ` seurer at gcc dot gnu.org 2020-09-08 19:54 ` seurer at gcc dot gnu.org 2020-09-08 20:52 ` bergner at gcc dot gnu.org 2020-09-09 9:48 ` ro at gcc dot gnu.org 2020-09-09 14:51 ` anlauf at gcc dot gnu.org 2020-09-09 14:54 ` anlauf at gcc dot gnu.org 2020-09-09 15:01 ` ro at CeBiTec dot Uni-Bielefeld.DE 2020-09-09 17:58 ` anlauf at gcc dot gnu.org 2020-09-09 19:03 ` bergner at gcc dot gnu.org 2020-09-10 12:50 ` ro at CeBiTec dot Uni-Bielefeld.DE 2020-09-10 17:29 ` anlauf at gcc dot gnu.org 2020-09-10 22:11 ` ro at CeBiTec dot Uni-Bielefeld.DE 2020-09-10 22:59 ` bergner at gcc dot gnu.org 2020-09-10 23:12 ` bergner at gcc dot gnu.org 2020-09-10 23:28 ` bergner at gcc dot gnu.org 2020-09-10 23:31 ` bergner at gcc dot gnu.org 2020-09-11 18:56 ` anlauf at gcc dot gnu.org 2020-09-11 19:47 ` segher at gcc dot gnu.org 2020-09-13 21:37 ` ro at CeBiTec dot Uni-Bielefeld.DE 2020-09-14 17:06 ` joseph at codesourcery dot com 2020-09-14 19:04 ` anlauf at gcc dot gnu.org 2020-09-14 20:04 ` anlauf at gcc dot gnu.org 2020-09-14 20:42 ` joseph at codesourcery dot com 2020-09-15 0:08 ` segher at gcc dot gnu.org 2020-10-03 15:15 ` dominiq at lps dot ens.fr 2020-10-03 18:57 ` ro at CeBiTec dot Uni-Bielefeld.DE 2020-10-16 12:07 ` rguenth at gcc dot gnu.org 2020-11-30 21:58 ` seurer at gcc dot gnu.org 2021-03-08 16:17 ` ebotcazou at gcc dot gnu.org 2021-03-10 11:32 ` cvs-commit at gcc dot gnu.org 2021-04-22 3:03 ` [Bug fortran/96983] [11/12 " cvs-commit at gcc dot gnu.org 2021-04-27 11:39 ` jakub at gcc dot gnu.org 2021-05-19 12:37 ` burnus at gcc dot gnu.org 2021-05-19 16:43 ` ro at CeBiTec dot Uni-Bielefeld.DE 2021-05-20 7:52 ` cvs-commit at gcc dot gnu.org 2021-05-20 8:06 ` cvs-commit at gcc dot gnu.org 2021-05-20 8:11 ` burnus at gcc dot gnu.org 2021-07-28 7:05 ` rguenth at gcc dot gnu.org 2022-03-17 2:02 ` cvs-commit at gcc dot gnu.org 2022-03-17 21:00 ` meissner at gcc dot gnu.org
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-96983-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).