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/103475] New: ICE in gfc_expr_attr, at fortran/primary.c:2782 Date: Mon, 29 Nov 2021 18:52:53 +0000 [thread overview] Message-ID: <bug-103475-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103475 Bug ID: 103475 Summary: ICE in gfc_expr_attr, at fortran/primary.c:2782 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: --- With option -Wall and a missing attribute allocatable or pointer : (affects version down to at least r5) (gcc configured with --enable-checking=yes) $ cat z1.f90 program p type t end type class(t) :: x y = x() end $ gfortran-12-20211128 -c z1.f90 -Wall z1.f90:4:16: 4 | class(t) :: x | 1 Error: CLASS variable 'x' at (1) must be dummy, allocatable or pointer f951: internal compiler error: Segmentation fault 0xf0942f crash_signal ../../gcc/toplev.c:322 0x842464 gfc_expr_attr(gfc_expr*) ../../gcc/fortran/primary.c:2782 0x7e02eb gfc_check_assign(gfc_expr*, gfc_expr*, int, bool) ../../gcc/fortran/expr.c:3734 0x84a6d5 resolve_ordinary_assign ../../gcc/fortran/resolve.c:11188 0x852a3c gfc_resolve_code(gfc_code*, gfc_namespace*) ../../gcc/fortran/resolve.c:12047 0x854f97 resolve_codes ../../gcc/fortran/resolve.c:17536 0x85505e gfc_resolve(gfc_namespace*) ../../gcc/fortran/resolve.c:17571 0x83d314 resolve_all_program_units ../../gcc/fortran/parse.c:6573 0x83d314 gfc_parse_file() ../../gcc/fortran/parse.c:6829 0x88b37f gfc_be_parse_file ../../gcc/fortran/f95-lang.c:216
next reply other threads:[~2021-11-29 18:52 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-29 18:52 gscfq@t-online.de [this message] 2021-11-29 19:44 ` [Bug fortran/103475] " kargl at gcc dot gnu.org 2022-01-18 20:53 ` anlauf at gcc dot gnu.org 2023-02-13 20:05 ` anlauf at gcc dot gnu.org 2023-02-13 21:06 ` cvs-commit at gcc dot gnu.org 2023-02-13 21:14 ` 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-103475-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).