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/102787] New: [12 regression] ICE in new test case gfortran.dg/reshape_shape_2.f90
Date: Fri, 15 Oct 2021 18:58:45 +0000	[thread overview]
Message-ID: <bug-102787-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102787

            Bug ID: 102787
           Summary: [12 regression] ICE in new test case
                    gfortran.dg/reshape_shape_2.f90
           Product: gcc
           Version: 12.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:b47490c572c5938f887b54240af6096a7c90f640, r12-4415
make  -k check-gcc-fortran
RUNTESTFLAGS="dg.exp=gfortran.dg/reshape_shape_2.f90"
FAIL: gfortran.dg/reshape_shape_2.f90   -O  (internal compiler error)
FAIL: gfortran.dg/reshape_shape_2.f90   -O   (test for errors, line 6)
FAIL: gfortran.dg/reshape_shape_2.f90   -O  (test for excess errors)
# of unexpected failures        3

This only seems to happen on BE systems from what I see.

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/powerpc64-unknown-linux-gnu/./libgfortran/
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gfortran.dg/reshape_shape_2.f90
-fdiagnostics-plain-output -fdiagnostics-plain-output -O -pedantic-errors -S -o
reshape_shape_2.s
f951: internal compiler error: Segmentation fault
0x10c4696b crash_signal
        /home/seurer/gcc/git/gcc-test/gcc/toplev.c:322
0x120494b0 __gmpn_mul_1
        /home/seurer/gcc/git/build/gcc-test/gmp/mpn/mul_1.c:50
0x12043433 __gmpz_mul
        /home/seurer/gcc/git/gcc-test/gmp/mpz/mul.c:89
0x1028bfaf gfc_check_reshape(gfc_expr*, gfc_expr*, gfc_expr*, gfc_expr*)
        /home/seurer/gcc/git/gcc-test/gcc/fortran/check.c:4874
0x102e76ab do_check
        /home/seurer/gcc/git/gcc-test/gcc/fortran/intrinsic.c:316
0x102e7bb3 check_specific
        /home/seurer/gcc/git/gcc-test/gcc/fortran/intrinsic.c:4799
0x102f5cd7 gfc_intrinsic_func_interface(gfc_expr*, int)
        /home/seurer/gcc/git/gcc-test/gcc/fortran/intrinsic.c:5036
0x10370dd3 resolve_unknown_f
        /home/seurer/gcc/git/gcc-test/gcc/fortran/resolve.c:2937
0x10370dd3 resolve_function
        /home/seurer/gcc/git/gcc-test/gcc/fortran/resolve.c:3281
0x10370dd3 gfc_resolve_expr(gfc_expr*)
        /home/seurer/gcc/git/gcc-test/gcc/fortran/resolve.c:7115
0x102cebeb gfc_reduce_init_expr(gfc_expr*)
        /home/seurer/gcc/git/gcc-test/gcc/fortran/expr.c:3125
0x102d332b gfc_match_init_expr(gfc_expr**)
        /home/seurer/gcc/git/gcc-test/gcc/fortran/expr.c:3173
0x102b2f17 variable_decl
        /home/seurer/gcc/git/gcc-test/gcc/fortran/decl.c:3016
0x102b2f17 gfc_match_data_decl()
        /home/seurer/gcc/git/gcc-test/gcc/fortran/decl.c:6325
0x103486a7 match_word
        /home/seurer/gcc/git/gcc-test/gcc/fortran/parse.c:67
0x1034950f decode_statement
        /home/seurer/gcc/git/gcc-test/gcc/fortran/parse.c:378
0x1034f847 next_free
        /home/seurer/gcc/git/gcc-test/gcc/fortran/parse.c:1388
0x1034f847 next_statement
        /home/seurer/gcc/git/gcc-test/gcc/fortran/parse.c:1620
0x10352fef parse_spec
        /home/seurer/gcc/git/gcc-test/gcc/fortran/parse.c:4159
0x10356c73 parse_progunit
        /home/seurer/gcc/git/gcc-test/gcc/fortran/parse.c:6125


commit b47490c572c5938f887b54240af6096a7c90f640
Author: Harald Anlauf <anlauf@gmx.de>
Date:   Thu Oct 14 20:19:50 2021 +0200

    Fortran: generate error message for negative elements in SHAPE array

             reply	other threads:[~2021-10-15 18:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-15 18:58 seurer at gcc dot gnu.org [this message]
2021-10-15 19:52 ` [Bug fortran/102787] " anlauf at gcc dot gnu.org
2021-10-15 20:37 ` anlauf at gcc dot gnu.org
2021-10-15 23:51 ` [Bug fortran/102787] " pinskia at gcc dot gnu.org
2021-10-16 12:24 ` dominiq at lps dot ens.fr
2021-10-16 12:26 ` dominiq at lps dot ens.fr
2021-10-17 20:10 ` anlauf at gcc dot gnu.org
2021-10-18 21:55 ` anlauf at gcc dot gnu.org
2021-10-20 20:58 ` anlauf at gcc dot gnu.org
2021-11-26 21:31 ` anlauf at gcc dot gnu.org
2021-11-30 20:19 ` anlauf at gcc dot gnu.org
2021-11-30 21:10 ` cvs-commit at gcc dot gnu.org
2021-11-30 21:19 ` anlauf at gcc dot gnu.org
2021-11-30 21:21 ` anlauf at gcc dot gnu.org
2021-12-04 22:06 ` cvs-commit at gcc dot gnu.org
2021-12-11 21:57 ` cvs-commit at gcc dot gnu.org
2021-12-11 21:59 ` anlauf 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-102787-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: link
Be 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).