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/107707] New: ICE in gfc_compare_actual_formal, at fortran/interface.cc:3284
Date: Tue, 15 Nov 2022 18:03:04 +0000	[thread overview]
Message-ID: <bug-107707-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 107707
           Summary: ICE in gfc_compare_actual_formal, at
                    fortran/interface.cc:3284
           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: ---

Affects versions down to at least r5 :


$ cat z1.f90
program p
   character(3), allocatable :: c
   c = 'abc'
   call s(c)
contains
   subroutine s(x)
      character(real(3)), allocatable :: x
   end
end


$ gfortran-13-20221106 -c z1.f90
z1.f90:7:16:

    7 |       character(real(3)), allocatable :: x
      |                1
Error: Expression at (1) must be of INTEGER type, found REAL
f951: internal compiler error: Segmentation fault
0xf4697f crash_signal
        ../../gcc/toplev.cc:314
0x80de4a gfc_compare_actual_formal(gfc_actual_arglist**, gfc_formal_arglist*,
int, int, bool, locus*)
        ../../gcc/fortran/interface.cc:3284
0x80e5e6 gfc_procedure_use(gfc_symbol*, gfc_actual_arglist**, locus*)
        ../../gcc/fortran/interface.cc:4167
0x87ad0a resolve_specific_s0
        ../../gcc/fortran/resolve.cc:3636
0x87ad0a resolve_specific_s
        ../../gcc/fortran/resolve.cc:3656
0x87ad0a resolve_call
        ../../gcc/fortran/resolve.cc:3810
0x87839f gfc_resolve_code(gfc_code*, gfc_namespace*)
        ../../gcc/fortran/resolve.cc:12231
0x87a387 resolve_codes
        ../../gcc/fortran/resolve.cc:17624
0x87a44e gfc_resolve(gfc_namespace*)
        ../../gcc/fortran/resolve.cc:17659
0x862214 resolve_all_program_units
        ../../gcc/fortran/parse.cc:6631
0x862214 gfc_parse_file()
        ../../gcc/fortran/parse.cc:6887
0x8b0c8f gfc_be_parse_file
        ../../gcc/fortran/f95-lang.cc:229

             reply	other threads:[~2022-11-15 18:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-15 18:03 gscfq@t-online.de [this message]
2022-11-15 18:52 ` [Bug fortran/107707] " kargl at gcc dot gnu.org
2022-11-16 21:16 ` anlauf at gcc dot gnu.org
2022-11-16 21:27 ` sgk at troutmask dot apl.washington.edu
2022-11-16 21:51 ` cvs-commit at gcc dot gnu.org
2022-11-16 22:03 ` kargl 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-107707-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).