* [Bug fortran/93482] ICE in gfc_resolve_character_array_constructor, at fortran/array.c:2096
[not found] <bug-93482-4@http.gcc.gnu.org/bugzilla/>
@ 2020-05-26 16:36 ` gscfq@t-online.de
2022-02-08 22:42 ` anlauf at gcc dot gnu.org
` (2 subsequent siblings)
3 siblings, 0 replies; 4+ messages in thread
From: gscfq@t-online.de @ 2020-05-26 16:36 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93482
--- Comment #2 from G. Steinmetz <gscfq@t-online.de> ---
Another test case :
$ cat z3.f90
program p
character(2), parameter :: a(3) = ['a1', 'b2', 'c3']
print *, [(a(2:1))]
print *, size([(a(2:1))])
end
Works without parameter attribute :
$ cat z4.f90
program p
character(2) :: a(3) = ['a1', 'b2', 'c3']
print *, [(a(2:1))]
print *, size([(a(2:1))])
end
$ gfortran-11-20200524 z4.f90 && ./a.out
0
$
^ permalink raw reply [flat|nested] 4+ messages in thread* [Bug fortran/93482] ICE in gfc_resolve_character_array_constructor, at fortran/array.c:2096
[not found] <bug-93482-4@http.gcc.gnu.org/bugzilla/>
2020-05-26 16:36 ` [Bug fortran/93482] ICE in gfc_resolve_character_array_constructor, at fortran/array.c:2096 gscfq@t-online.de
@ 2022-02-08 22:42 ` anlauf at gcc dot gnu.org
2022-06-07 17:37 ` kargl at gcc dot gnu.org
2022-08-28 20:16 ` anlauf at gcc dot gnu.org
3 siblings, 0 replies; 4+ messages in thread
From: anlauf at gcc dot gnu.org @ 2022-02-08 22:42 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93482
anlauf at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |anlauf at gcc dot gnu.org
Status|NEW |WAITING
--- Comment #3 from anlauf at gcc dot gnu.org ---
Seems to have been fixed on mainline, and backported to 11- and 10-branch.
Likely a duplicate.
^ permalink raw reply [flat|nested] 4+ messages in thread* [Bug fortran/93482] ICE in gfc_resolve_character_array_constructor, at fortran/array.c:2096
[not found] <bug-93482-4@http.gcc.gnu.org/bugzilla/>
2020-05-26 16:36 ` [Bug fortran/93482] ICE in gfc_resolve_character_array_constructor, at fortran/array.c:2096 gscfq@t-online.de
2022-02-08 22:42 ` anlauf at gcc dot gnu.org
@ 2022-06-07 17:37 ` kargl at gcc dot gnu.org
2022-08-28 20:16 ` anlauf at gcc dot gnu.org
3 siblings, 0 replies; 4+ messages in thread
From: kargl at gcc dot gnu.org @ 2022-06-07 17:37 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93482
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kargl at gcc dot gnu.org
--- Comment #4 from kargl at gcc dot gnu.org ---
Here is z1.f90 converted to a suitable testcase.
! { dg-do run }
program p
if (size([[character::]]) /= 0) stop 1
end
Here is z2.f90 converted to a suitable testcase.
! { dg-do run }
program p
integer :: i
character, parameter :: c(0) = 'a'
if (size([[c]]) /= 0) stop 1
if (size([[('b',i=1,0)]]) /= 0) stop 2
end
^ permalink raw reply [flat|nested] 4+ messages in thread* [Bug fortran/93482] ICE in gfc_resolve_character_array_constructor, at fortran/array.c:2096
[not found] <bug-93482-4@http.gcc.gnu.org/bugzilla/>
` (2 preceding siblings ...)
2022-06-07 17:37 ` kargl at gcc dot gnu.org
@ 2022-08-28 20:16 ` anlauf at gcc dot gnu.org
3 siblings, 0 replies; 4+ messages in thread
From: anlauf at gcc dot gnu.org @ 2022-08-28 20:16 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93482
anlauf at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution|--- |FIXED
--- Comment #5 from anlauf at gcc dot gnu.org ---
(In reply to anlauf from comment #3)
> Seems to have been fixed on mainline, and backported to 11- and 10-branch.
> Likely a duplicate.
Some issues with zero-sized constructors as in comment#2 have been fixed for
pr103692.
There have been fixes for other issues with constructors, including nested
constructors. I believe there is sufficient coverage for trivial cases like
those in this PR, and it would be beneficial to have a clean, separate PR
for remaining problems. Closing this one.
Thanks for the report!
^ permalink raw reply [flat|nested] 4+ messages in thread