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/95502] New: ICE in gfc_check_do_variable, at fortran/parse.c:4446
Date: Wed, 03 Jun 2020 15:44:47 +0000	[thread overview]
Message-ID: <bug-95502-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 95502
           Summary: ICE in gfc_check_do_variable, at fortran/parse.c:4446
           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
   integer, pointer :: z
   nullify(z%kind)
end


$ cat z2.f90
program p
   complex, pointer :: z
   nullify(z%kind)
   ! nullify(z%re)
   ! nullify(z%im)
end


$ cat z3.f90
program p
   character, pointer :: z
   nullify(z%len)
   nullify(z%kind)
end


$ gfortran-11-20200531 -c z1.f90
f951: internal compiler error: Segmentation fault
0xbc37bf crash_signal
        ../../gcc/toplev.c:328
0x6aeed8 gfc_check_do_variable(gfc_symtree*)
        ../../gcc/fortran/parse.c:4446
0x6895ab gfc_match_nullify()
        ../../gcc/fortran/match.c:4625
0x6a7651 match_word
        ../../gcc/fortran/parse.c:65
0x6ab35d decode_statement
        ../../gcc/fortran/parse.c:527
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:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-03 15:44 gscfq@t-online.de [this message]
2020-06-03 16:52 ` [Bug fortran/95502] " kargl at gcc dot gnu.org
2020-06-09 11:40 ` marxin at gcc dot gnu.org
2021-06-04 21:13 ` anlauf at gcc dot gnu.org
2021-06-16 19:54 ` cvs-commit at gcc dot gnu.org
2021-06-16 20:05 ` cvs-commit at gcc dot gnu.org
2021-06-18 18:21 ` cvs-commit at gcc dot gnu.org
2021-06-18 18:42 ` cvs-commit at gcc dot gnu.org
2021-06-18 18:45 ` 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-95502-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).