public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aarograh at umich dot edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/85541] ICE with parameterized derived type (PDT) and allocate Date: Thu, 13 Oct 2022 16:30:31 +0000 [thread overview] Message-ID: <bug-85541-4-5syTAd18cJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-85541-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85541 aarograh at umich dot edu changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aarograh at umich dot edu --- Comment #4 from aarograh at umich dot edu --- I've also encountered issues with this in gcc 8.3. Here's my even simpler example that shows the error. The commented code hints at the more complex functionality that I'm actually working toward. MODULE testMod IMPLICIT NONE PUBLIC TYPE :: cache(n) INTEGER,LEN :: n REAL :: a(n) ENDTYPE cache TYPE :: parent TYPE(cache(1)),ALLOCATABLE :: cache ENDTYPE parent ENDMODULE testMod PROGRAM test USE testMod TYPE(cache(1)),ALLOCATABLE :: testcache TYPE(parent) :: testparent ALLOCATE(cache(1) :: testcache) WRITE(*,*) testcache%n WRITE(*,*) testcache%a !ALLOCATE(cache(1) :: testparent%cache) !WRITE(*,*) testparent%cache%n !WRITE(*,*) testparent%cache%a ENDPROGRAM test f951: internal compiler error: in gfc_get_derived_type, at fortran/trans-types.c:2545 0x5c6ca5 gfc_get_derived_type(gfc_symbol*, int) ../../gcc-8.3.0-source/gcc/fortran/trans-types.c:2545 0x748aa8 gfc_get_derived_type(gfc_symbol*, int) ../../gcc-8.3.0-source/gcc/fortran/trans-types.c:2691 0x749498 gfc_typenode_for_spec(gfc_typespec*, int) ../../gcc-8.3.0-source/gcc/fortran/trans-types.c:1203 0x74975c gfc_sym_type(gfc_symbol*) ../../gcc-8.3.0-source/gcc/fortran/trans-types.c:2272 0x74975c gfc_sym_type(gfc_symbol*) ../../gcc-8.3.0-source/gcc/fortran/trans-types.c:2230 0x6f443d gfc_get_symbol_decl(gfc_symbol*) ../../gcc-8.3.0-source/gcc/fortran/trans-decl.c:1739 0x6f6ff8 gfc_create_module_variable ../../gcc-8.3.0-source/gcc/fortran/trans-decl.c:5024 0x6f6ff8 gfc_create_module_variable ../../gcc-8.3.0-source/gcc/fortran/trans-decl.c:4941 0x6bd202 do_traverse_symtree ../../gcc-8.3.0-source/gcc/fortran/symbol.c:4179 0x6f98b3 gfc_generate_module_vars(gfc_namespace*) ../../gcc-8.3.0-source/gcc/fortran/trans-decl.c:5496 0x6d5459 gfc_generate_module_code(gfc_namespace*) ../../gcc-8.3.0-source/gcc/fortran/trans.c:2201 0x6886bb translate_all_program_units ../../gcc-8.3.0-source/gcc/fortran/parse.c:6112 0x6886bb gfc_parse_file() ../../gcc-8.3.0-source/gcc/fortran/parse.c:6328 0x6cefbf gfc_be_parse_file ../../gcc-8.3.0-source/gcc/fortran/f95-lang.c:204 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See <https://gcc.gnu.org/bugs/> for instructions.
prev parent reply other threads:[~2022-10-13 16:30 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-85541-4@http.gcc.gnu.org/bugzilla/> 2020-06-28 0:22 ` siteg at mathalacarte dot com 2022-10-13 16:30 ` aarograh at umich dot edu [this message]
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-85541-4-5syTAd18cJ@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).