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/104332] New: [9/10/11/12 Regression] ICE in resolve_symbol, at fortran/resolve.cc:15815
Date: Tue, 01 Feb 2022 17:41:43 +0000	[thread overview]
Message-ID: <bug-104332-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 104332
           Summary: [9/10/11/12 Regression] ICE in resolve_symbol, at
                    fortran/resolve.cc:15815
           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 r8 (ifort/ifx rejects it) :


$ cat z1.f90
block data
   bind(c) a
end


$ gfortran-7 -c z1.f90
$
$ gfortran-12-20220130 -c z1.f90
f951: internal compiler error: Segmentation fault
0xcc655f crash_signal
        ../../gcc/toplev.cc:322
0x76b037 resolve_symbol
        ../../gcc/fortran/resolve.cc:15815
0x789ca2 do_traverse_symtree
        ../../gcc/fortran/symbol.cc:4174
0x76e024 resolve_types
        ../../gcc/fortran/resolve.cc:17455
0x7694bc gfc_resolve(gfc_namespace*)
        ../../gcc/fortran/resolve.cc:17570
0x7515f2 gfc_parse_file()
        ../../gcc/fortran/parse.cc:6792
0x79eecf gfc_be_parse_file
        ../../gcc/fortran/f95-lang.cc:216

             reply	other threads:[~2022-02-01 17:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-01 17:41 gscfq@t-online.de [this message]
2022-02-01 17:42 ` [Bug fortran/104332] " gscfq@t-online.de
2022-02-01 19:14 ` kargl at gcc dot gnu.org
2022-02-01 20:04 ` kargl at gcc dot gnu.org
2022-02-01 20:04 ` kargl at gcc dot gnu.org
2022-02-01 20:53 ` sgk at troutmask dot apl.washington.edu
2022-02-02  7:12 ` rguenth at gcc dot gnu.org
2022-05-27  9:47 ` [Bug fortran/104332] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:47 ` jakub at gcc dot gnu.org
2023-03-08 21:59 ` anlauf at gcc dot gnu.org
2023-03-09 18:08 ` anlauf at gcc dot gnu.org
2023-03-10 17:56 ` cvs-commit at gcc dot gnu.org
2023-03-15 20:46 ` cvs-commit at gcc dot gnu.org
2023-03-17 20:40 ` cvs-commit at gcc dot gnu.org
2023-03-17 20:41 ` cvs-commit at gcc dot gnu.org
2023-03-17 20:42 ` 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-104332-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).