public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/95503] New: ICE in gfc_is_simply_contiguous, at fortran/expr.c:5844
Date: Wed, 03 Jun 2020 15:46:03 +0000	[thread overview]
Message-ID: <bug-95503-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 95503
           Summary: ICE in gfc_is_simply_contiguous, at
                    fortran/expr.c:5844
           Product: gcc
           Version: 11.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: gscfq@t-online.de
  Target Milestone: ---

Changed between 20181028 (error) and 20181104 (ICE) :


$ cat z1.f90
program p
   complex, target :: a = (1.0, 2.0)
   real, pointer, contiguous :: b => a%re
end


$ cat z2.f90
program p
   complex, target :: a
   real, pointer, contiguous :: b => a%re
end


$ gfortran-11-20200531 -c z1.f90
f951: internal compiler error: in gfc_is_simply_contiguous, at
fortran/expr.c:5844
0x65d5a2 gfc_is_simply_contiguous(gfc_expr*, bool, bool)
        ../../gcc/fortran/expr.c:5844
0x65e5f7 gfc_check_pointer_assign(gfc_expr*, gfc_expr*, bool, bool)
        ../../gcc/fortran/expr.c:4349
0x65e93d gfc_check_assign_symbol(gfc_symbol*, gfc_component*, gfc_expr*)
        ../../gcc/fortran/expr.c:4438
0x63d70e add_init_expr_to_sym
        ../../gcc/fortran/decl.c:1926
0x64762a variable_decl
        ../../gcc/fortran/decl.c:2990
0x64762a gfc_match_data_decl()
        ../../gcc/fortran/decl.c:6190
0x6aa9d3 match_word
        ../../gcc/fortran/parse.c:65
0x6aa9d3 decode_statement
        ../../gcc/fortran/parse.c:376
0x6ac41a next_free
        ../../gcc/fortran/parse.c:1279
0x6ac41a next_statement
        ../../gcc/fortran/parse.c:1511
0x6ada6b parse_spec
        ../../gcc/fortran/parse.c:3922
0x6b083c parse_progunit
        ../../gcc/fortran/parse.c:5851
0x6b1f19 gfc_parse_file()
        ../../gcc/fortran/parse.c:6392
0x6fdfff gfc_be_parse_file
        ../../gcc/fortran/f95-lang.c:210

             reply	other threads:[~2020-06-03 15:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-03 15:46 gscfq@t-online.de [this message]
2020-06-03 18:40 ` [Bug fortran/95503] " anlauf at gcc dot gnu.org
2020-06-03 22:04 ` [Bug fortran/95503] [9/10/11 Regression] " tkoenig at gcc dot gnu.org
2020-06-04 18:48 ` anlauf at gcc dot gnu.org
2020-06-11 13:49 ` cvs-commit at gcc dot gnu.org
2020-06-14 12:40 ` cvs-commit at gcc dot gnu.org
2020-06-14 13:04 ` cvs-commit at gcc dot gnu.org
2020-06-14 13:28 ` 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-95503-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).