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/105243] New: ICE in next_char, at fortran/io.cc:160
Date: Tue, 12 Apr 2022 17:21:39 +0000	[thread overview]
Message-ID: <bug-105243-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 105243
           Summary: ICE in next_char, at fortran/io.cc:160
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: gscfq@t-online.de
  Target Milestone: ---

Affects versions down to at least r5 :


$ cat z1.f90
program p
   type t
      character(3) :: c = '(a)'
   end type
   class(t), parameter :: x = 1.
   print x%c
end


$ gfortran-12-20220410 -c z1.f90
f951: internal compiler error: Segmentation fault
0xcce66f crash_signal
        ../../gcc/toplev.cc:322
0x713d78 next_char
        ../../gcc/fortran/io.cc:160
0x713ef6 next_char
        ../../gcc/fortran/io.cc:214
0x713ef6 next_char_not_space
        ../../gcc/fortran/io.cc:208
0x713f2a format_lex
        ../../gcc/fortran/io.cc:236
0x714522 format_lex
        ../../gcc/fortran/io.cc:617
0x714522 check_format
        ../../gcc/fortran/io.cc:619
0x716ab7 check_format_string
        ../../gcc/fortran/io.cc:1338
0x716ab7 match_io
        ../../gcc/fortran/io.cc:4409
0x71a1ba gfc_match_print()
        ../../gcc/fortran/io.cc:4450
0x74aa31 match_word
        ../../gcc/fortran/parse.cc:67
0x750563 decode_statement
        ../../gcc/fortran/parse.cc:539
0x75099a next_free
        ../../gcc/fortran/parse.cc:1397
0x75099a next_statement
        ../../gcc/fortran/parse.cc:1629
0x751f2b parse_spec
        ../../gcc/fortran/parse.cc:4168
0x7550cc parse_progunit
        ../../gcc/fortran/parse.cc:6210
0x756791 gfc_parse_file()
        ../../gcc/fortran/parse.cc:6755
0x7a438f gfc_be_parse_file
        ../../gcc/fortran/f95-lang.cc:216

             reply	other threads:[~2022-04-12 17:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-12 17:21 gscfq@t-online.de [this message]
2022-04-12 17:22 ` [Bug fortran/105243] " gscfq@t-online.de
2022-05-16  0:06 ` kargl at gcc dot gnu.org
2022-05-16 20:27 ` anlauf at gcc dot gnu.org
2022-05-16 21:06 ` anlauf at gcc dot gnu.org
2022-05-16 22:16 ` sgk at troutmask dot apl.washington.edu
2022-05-16 22:22 ` sgk at troutmask dot apl.washington.edu
2022-05-17 19:56 ` anlauf at gcc dot gnu.org
2022-05-17 23:21 ` sgk at troutmask dot apl.washington.edu
2022-06-29 19:42 ` anlauf at gcc dot gnu.org
2022-06-29 19:54 ` anlauf at gcc dot gnu.org
2022-06-29 20:27 ` sgk at troutmask dot apl.washington.edu
2022-06-30 19:01 ` cvs-commit at gcc dot gnu.org
2022-07-03 19:44 ` cvs-commit at gcc dot gnu.org
2022-07-03 20:13 ` cvs-commit at gcc dot gnu.org
2022-07-03 20:29 ` cvs-commit at gcc dot gnu.org
2022-07-03 20:33 ` 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-105243-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).