Event ID: 1 name: checkpoint eventReferenceDateTime 1979-01-01T00:00:00.000 eventFirstDateTime 1979-01-01T00:00:00.000 eventLastDateTime 1979-01-01T00:16:00.000 eventInterval PT08M eventOffset PT00.000S triggerNextEventDateTime 1979-01-01T00:00:00.000 neverTriggerEvent F triggerCurrentEvent F nextEventIsFirst T lastEventWasFinal F eventisFirstInDay F eventisFirstInMonth F eventisFirstInYear F eventisLastInDay F eventisLastInMonth F eventisLastInYear F
this is a pgi compiler bug. it is unclear how and when this can be fixed. a simple reproducer, i.e. by using mo_generic_linked_list is not showing the buggy behaviour.
stack:
#0 0x00000000017ee83b in mo_event_group::t_eventgroup_getnextevent (current_item=...) at src/shared/mo_event_group.f90:157#1 0x00000000017edc61 in mo_event_manager::printeventgroup (handle=<optimized out>) at src/shared/mo_event_manager.f90:127#2 0x000000000060d08b in mo_nh_stepping::perform_nh_timeloop (mtime_current=..., latbc=...) at src/atm_dyn_iconam/mo_nh_stepping.f90:742#3 0x000000000060c4ee in mo_nh_stepping::perform_nh_stepping (mtime_current=..., latbc=...) at src/atm_dyn_iconam/mo_nh_stepping.f90:576
at src/shared/mo_event_group.f90:156156 p => current_item%next()
(line numbers differ slightly due to debugging additions)