public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
* [Bug fortran/96386] New: Internal compiler error in ASSOCIATE @ 2020-07-30 6:39 m.deij at marin dot nl 2020-07-30 7:47 ` [Bug fortran/96386] " marxin at gcc dot gnu.org ` (2 more replies) 0 siblings, 3 replies; 4+ messages in thread From: m.deij at marin dot nl @ 2020-07-30 6:39 UTC (permalink / raw) To: gcc-bugs https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96386 Bug ID: 96386 Summary: Internal compiler error in ASSOCIATE Product: gcc Version: 9.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: m.deij at marin dot nl Target Milestone: --- The code below triggers an ICE with the message f951: internal compiler error: find_array_spec(): Missing spec Note that older version of the compiler (I could test 6.3.1) does not give an ICE, but newer versions (I have access to 8.3.1 and 9.2.0) do have this problem. MODULE assoc TYPE Level3 INTEGER :: someNumber END TYPE Level3 TYPE Level2 INTEGER :: nLevel3 TYPE (Level3), ALLOCATABLE :: levels3(:) END TYPE Level2 TYPE Level1 INTEGER :: nLevel2 TYPE (Level2), ALLOCATABLE :: levels2(:) END TYPE Level1 TYPE outer_type INTEGER :: nLevel1 TYPE (Level1), ALLOCATABLE :: levels1(:) END TYPE outer_type TYPE(outer_type), TARGET :: outer CONTAINS SUBROUTINE internal_compiler_error_repro() INTEGER F,B,Z ASSOCIATE(l1 => outer%levels1 ) ! <-- this gives an ICE !ASSOCIATE(l1 => outer%levels1(:) ) ! <-- No ICE if array spec is added DO F=1,outer%nLevel1 ASSOCIATE(l2 => l1(F)%levels2 ) DO B=1,l2(F)%nLevel3 ! <-- condition for ICE to be triggered END DO END ASSOCIATE END DO END ASSOCIATE END SUBROUTINE internal_compiler_error_repro END MODULE ^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug fortran/96386] Internal compiler error in ASSOCIATE 2020-07-30 6:39 [Bug fortran/96386] New: Internal compiler error in ASSOCIATE m.deij at marin dot nl @ 2020-07-30 7:47 ` marxin at gcc dot gnu.org 2021-01-25 19:30 ` tkoenig at gcc dot gnu.org 2021-01-25 20:56 ` paul.richard.thomas at gmail dot com 2 siblings, 0 replies; 4+ messages in thread From: marxin at gcc dot gnu.org @ 2020-07-30 7:47 UTC (permalink / raw) To: gcc-bugs https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96386 Martin Liška <marxin at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2020-07-30 Ever confirmed|0 |1 CC| |marxin at gcc dot gnu.org, | |pault at gcc dot gnu.org Status|UNCONFIRMED |NEW --- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> --- Confirmed, started with r8-3365-gb89a63b916340ef2. ^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug fortran/96386] Internal compiler error in ASSOCIATE 2020-07-30 6:39 [Bug fortran/96386] New: Internal compiler error in ASSOCIATE m.deij at marin dot nl 2020-07-30 7:47 ` [Bug fortran/96386] " marxin at gcc dot gnu.org @ 2021-01-25 19:30 ` tkoenig at gcc dot gnu.org 2021-01-25 20:56 ` paul.richard.thomas at gmail dot com 2 siblings, 0 replies; 4+ messages in thread From: tkoenig at gcc dot gnu.org @ 2021-01-25 19:30 UTC (permalink / raw) To: gcc-bugs https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96386 Thomas Koenig <tkoenig at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED CC| |tkoenig at gcc dot gnu.org Status|NEW |RESOLVED --- Comment #2 from Thomas Koenig <tkoenig at gcc dot gnu.org> --- The code has been fixed in the meantime. I have committed the test case as r11-6899-g7d54cccad332074d5fb81123796239f0f61b11a7 to make sure there is no regression. Thanks for the bug report! ^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug fortran/96386] Internal compiler error in ASSOCIATE 2020-07-30 6:39 [Bug fortran/96386] New: Internal compiler error in ASSOCIATE m.deij at marin dot nl 2020-07-30 7:47 ` [Bug fortran/96386] " marxin at gcc dot gnu.org 2021-01-25 19:30 ` tkoenig at gcc dot gnu.org @ 2021-01-25 20:56 ` paul.richard.thomas at gmail dot com 2 siblings, 0 replies; 4+ messages in thread From: paul.richard.thomas at gmail dot com @ 2021-01-25 20:56 UTC (permalink / raw) To: gcc-bugs https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96386 --- Comment #3 from paul.richard.thomas at gmail dot com <paul.richard.thomas at gmail dot com> --- Hi Thomas, When did it get fixed? I seem to have done so many associate fixes that I barely know where to start - was it even me? Lots of the recent PRs are low lying fruit. It's pleasing to see patches of a few lines doing the job :-) Are you on to teams now? Cheers Paul On Mon, 25 Jan 2021 at 19:36, tkoenig at gcc dot gnu.org < gcc-bugzilla@gcc.gnu.org> wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96386 > > Thomas Koenig <tkoenig at gcc dot gnu.org> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Resolution|--- |FIXED > CC| |tkoenig at gcc dot > gnu.org > Status|NEW |RESOLVED > > --- Comment #2 from Thomas Koenig <tkoenig at gcc dot gnu.org> --- > The code has been fixed in the meantime. I have committed the > test case as r11-6899-g7d54cccad332074d5fb81123796239f0f61b11a7 > to make sure there is no regression. > > Thanks for the bug report! > > -- > You are receiving this mail because: > You are on the CC list for the bug. ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2021-01-25 20:56 UTC | newest] Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2020-07-30 6:39 [Bug fortran/96386] New: Internal compiler error in ASSOCIATE m.deij at marin dot nl 2020-07-30 7:47 ` [Bug fortran/96386] " marxin at gcc dot gnu.org 2021-01-25 19:30 ` tkoenig at gcc dot gnu.org 2021-01-25 20:56 ` paul.richard.thomas at gmail dot com
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).