Hi all, hi Harald, thanks for the review. I choose to use gfc_replace_expr() and retested. Everything went fine now. Also thank you clarifying the pdt as a component in a derived type and that that is still a bug and I didn't do it wrong. I have pushed the attached patch seconds ago. Thanks for your help, Andre On Tue, 11 Jul 2023 22:24:37 +0200 Harald Anlauf wrote: > Hi Andre, > > this looks much better now! > > This looks mostly good to me, except for a typo in the testcase: > > + if (p% ci% len /= 42) stop 4 > > There is no component "ci", only "c". The testsuite would fail. > > Regarding the memleak: replacing > > // TODO: Fix leaking expr tmp, when simplify is done twice. > tmp = gfc_copy_expr (*newp); > > by > > if (inquiry->next) > { > gfc_free_expr (tmp); > tmp = gfc_copy_expr (*newp); > } > > or rather > > if (inquiry->next) > gfc_replace_expr (tmp, *newp); > > at least shrinks the leak a bit. (Untested otherwise). > > OK with one of the above changes (provided it survives regtesting). > > Thanks for the patch! > > Harald > > > Am 11.07.23 um 18:23 schrieb Andre Vehreschild via Gcc-patches: > > Hi Harald, > > > > attached is a new version of the patch. This now also respects inquiry-LEN. > > Btw, there is a potential memory leak in the simplify for inquiry > > functions. I have added a note into the code. > > > > I tried to use a pdt within a derived type as a component. Is that not > > allowed by the standard? I know, I could hunt in the standard for it, but > > when someone knows out of his head, he could greatly help me out. > > > > Regtests ok on x86_64-linux-gnu/F37. > > > > Regards, > > Andre > > > > On Mon, 10 Jul 2023 20:55:29 +0200 > > Harald Anlauf wrote: > > > >> Hi Andre, > >> > >> thanks for looking into this! > >> > >> While it fixes the original PR, here is a minor extension of the > >> testcase that ICEs here with your patch: > >> > >> program pr102003 > >> type pdt(n) > >> integer, len :: n = 8 > >> character(len=n) :: c > >> end type pdt > >> type(pdt(42)) :: p > >> integer, parameter :: m = len (p% c) > >> integer, parameter :: n = p% c% len > >> > >> if (m /= 42) stop 1 > >> if (len (p% c) /= 42) stop 2 > >> print *, p% c% len ! OK > >> if (p% c% len /= 42) stop 3 ! OK > >> print *, n ! ICE > >> end > >> > >> I get: > >> > >> pdt_33.f03:14:27: > >> > >> 14 | integer, parameter :: n = p% c% len > >> | 1 > >> Error: non-constant initialization expression at (1) > >> pdt_33.f03:20:31: > >> > >> 20 | print *, n ! ICE > >> | 1 > >> internal compiler error: tree check: expected record_type or union_type > >> or qual_union_type, have integer_type in gfc_conv_component_ref, at > >> fortran/trans-expr.cc:2757 > >> 0x84286c tree_check_failed(tree_node const*, char const*, int, char > >> const*, ...) > >> ../../gcc-trunk/gcc/tree.cc:8899 > >> 0xa6d6fb tree_check3(tree_node*, char const*, int, char const*, > >> tree_code, tree_code, tree_code) > >> ../../gcc-trunk/gcc/tree.h:3617 > >> 0xa90847 gfc_conv_component_ref(gfc_se*, gfc_ref*) > >> ../../gcc-trunk/gcc/fortran/trans-expr.cc:2757 > >> 0xa91bbc gfc_conv_variable > >> ../../gcc-trunk/gcc/fortran/trans-expr.cc:3137 > >> 0xaa8e9c gfc_conv_expr(gfc_se*, gfc_expr*) > >> ../../gcc-trunk/gcc/fortran/trans-expr.cc:9594 > >> 0xaa92ae gfc_conv_expr_reference(gfc_se*, gfc_expr*) > >> ../../gcc-trunk/gcc/fortran/trans-expr.cc:9713 > >> 0xad67f6 gfc_trans_transfer(gfc_code*) > >> ../../gcc-trunk/gcc/fortran/trans-io.cc:2607 > >> 0xa43cb7 trans_code > >> ../../gcc-trunk/gcc/fortran/trans.cc:2449 > >> 0xad37c6 build_dt > >> ../../gcc-trunk/gcc/fortran/trans-io.cc:2051 > >> 0xa43cd7 trans_code > >> ../../gcc-trunk/gcc/fortran/trans.cc:2421 > >> 0xa84711 gfc_generate_function_code(gfc_namespace*) > >> ../../gcc-trunk/gcc/fortran/trans-decl.cc:7762 > >> 0x9d9ca7 translate_all_program_units > >> ../../gcc-trunk/gcc/fortran/parse.cc:6929 > >> 0x9d9ca7 gfc_parse_file() > >> ../../gcc-trunk/gcc/fortran/parse.cc:7235 > >> 0xa40a1f gfc_be_parse_file > >> ../../gcc-trunk/gcc/fortran/f95-lang.cc:229 > >> > >> The fortran-dump confirms that n is not simplified to a constant. > >> So while you're at it, do you also see a solution to this variant? > >> > >> Harald > >> > >> > >> Am 10.07.23 um 17:48 schrieb Andre Vehreschild via Gcc-patches: > >>> Hi all, > >>> > >>> while browsing the pdt meta-bug I came across 102003 and thought to > >>> myself: Well, that one is easy. How foolish of me... > >>> > >>> Anyway, the solution attached prevents a pdt_len (or pdt_kind) expression > >>> in a function call (e.g. len() or kind()) to mark the whole expression as > >>> a pdt one. The second part of the patch in simplify.cc then takes care of > >>> either generating the correct component ref or when a constant expression > >>> (i.e. gfc_init_expr_flag is set) is required to look this up from the > >>> actual symbol (not from the type, because there the default value is > >>> stored). > >>> > >>> Regtested ok on x86_64-linux-gnu/Fedora 37. > >>> > >>> Regards, > >>> Andre > >>> -- > >>> Andre Vehreschild * Email: vehre ad gmx dot de > >> > > > > > > -- > > Andre Vehreschild * Email: vehre ad gmx dot de > -- Andre Vehreschild * Email: vehre ad gmx dot de