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/104314] New: ICE in deferred_op_assign, at fortran/resolve.cc:11794 Date: Mon, 31 Jan 2022 20:03:41 +0000 [thread overview] Message-ID: <bug-104314-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104314 Bug ID: 104314 Summary: ICE in deferred_op_assign, at fortran/resolve.cc:11794 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 character(:), allocatable :: c(:) c = ['123'] c = c == c end $ gfortran-12-20220130 -c z1.f90 z1.f90:4:7: 4 | c = c == c | 1 Error: Cannot convert LOGICAL(4) to CHARACTER(0) at (1) f951: internal compiler error: Segmentation fault 0xe6e49f crash_signal ../../gcc/toplev.cc:322 0x7a979c deferred_op_assign ../../gcc/fortran/resolve.cc:11794 0x7a979c gfc_resolve_code(gfc_code*, gfc_namespace*) ../../gcc/fortran/resolve.cc:12063 0x7a98e7 resolve_codes ../../gcc/fortran/resolve.cc:17537 0x7a99ae gfc_resolve(gfc_namespace*) ../../gcc/fortran/resolve.cc:17572 0x791cd4 resolve_all_program_units ../../gcc/fortran/parse.cc:6586 0x791cd4 gfc_parse_file() ../../gcc/fortran/parse.cc:6842 0x7dff7f gfc_be_parse_file ../../gcc/fortran/f95-lang.cc:216
next reply other threads:[~2022-01-31 20:03 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-31 20:03 gscfq@t-online.de [this message] 2022-01-31 20:14 ` [Bug fortran/104314] " kargl at gcc dot gnu.org 2022-01-31 21:17 ` sgk at troutmask dot apl.washington.edu 2022-09-05 21:00 ` anlauf at gcc dot gnu.org 2022-09-15 20:15 ` cvs-commit at gcc dot gnu.org 2022-09-15 20:24 ` 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-104314-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: linkBe 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).