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/107923] New: ICE in lookup_function_fuzzy_find_candidates / check_interface0
Date: Tue, 29 Nov 2022 17:57:02 +0000	[thread overview]
Message-ID: <bug-107923-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 107923
           Summary: ICE in lookup_function_fuzzy_find_candidates /
                    check_interface0
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: gscfq@t-online.de
  Target Milestone: ---

Some older versions/snapshots show an ICE, some don't :


$ cat z1.f90
program p
   interface s
      module procedure a, b, a
   end interface
   call s
end


$ cat z2.f90
program p
   interface s
      module procedure a, b, a
   end interface
end


$ cat z3.f90
program p
   interface operator (.op.)
      procedure a b
   end interface
contains
end


$ cat z4.f90
module m
   interface s
      procedure a b
   end interface
end


$ gfortran-13-20221127 -c z1.f90
z1.f90:3:30:

    3 |       module procedure a, b, a
      |                              1
Error: Entity 'a' at (1) is already present in the interface
f951: internal compiler error: Segmentation fault
0xf36d0f crash_signal
        ../../gcc/toplev.cc:314
0x86e2fd lookup_function_fuzzy_find_candidates
        ../../gcc/fortran/resolve.cc:2943
0x86e328 lookup_function_fuzzy_find_candidates
        ../../gcc/fortran/resolve.cc:2949
0x872d88 gfc_lookup_function_fuzzy(char const*, gfc_symtree*)
        ../../gcc/fortran/resolve.cc:2964
0x80ad0e check_interface0
        ../../gcc/fortran/interface.cc:1885
0x80e913 check_sym_interfaces
        ../../gcc/fortran/interface.cc:2021
0x89ee32 do_traverse_symtree
        ../../gcc/fortran/symbol.cc:4180
0x80ea20 gfc_check_interfaces(gfc_namespace*)
        ../../gcc/fortran/interface.cc:2132
0x88318d resolve_types
        ../../gcc/fortran/resolve.cc:17562
0x87e4bc gfc_resolve(gfc_namespace*)
        ../../gcc/fortran/resolve.cc:17661
0x866294 resolve_all_program_units
        ../../gcc/fortran/parse.cc:6631
0x866294 gfc_parse_file()
        ../../gcc/fortran/parse.cc:6887
0x8b4d3f gfc_be_parse_file
        ../../gcc/fortran/f95-lang.cc:229

             reply	other threads:[~2022-11-29 17:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-29 17:57 gscfq@t-online.de [this message]
2022-11-29 17:57 ` [Bug fortran/107923] " gscfq@t-online.de
2022-11-30 12:42 ` marxin at gcc dot gnu.org
2023-08-30 19:38 ` mikael 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-107923-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).