Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
29386 Discussions

'Core dumped' error using ifx/ifort for recursive type with source allocation and array constructor

FlyingHermes
New Contributor I
777 Views

Hi,

Here is a compiler bug affecting both ifort andf ifx:

 

Module MyModule
  implicit none
  Type                          ::  MyType
    ! No error if next line is commented
    type(MyType)  ,allocatable  ::  Items(:)
  End Type
  contains
  Subroutine MySub()
    type(MyType) ,allocatable ::  List(:), Items(:)
    allocate( List, source = [Items]  )
    ! No error if above line replaced with:
    ! allocate( List, source = Items )
  End Subroutine
End Module

 

Note that there is no compilation error if:

  • the recursion in the derived-type is removed by commenting the component 'Items' or
  • the array constructor is removed in the allocate statement by removing the square brackets around 'Items'.

The output using ifx is:

ifx version 2025.0.4
ifx: error #10105: /home/opt/INTEL/oneapi/compiler/2025.0/bin/compiler/xfortcom: core dumped
ifx: warning #10102: unknown signal(-1102185024)
ifx: error #10106: Fatal error in /home/opt/INTEL/oneapi/compiler/2025.0/bin/compiler/xfortcom, terminated by unknown
compilation aborted for MyModule.F90 (code 1)

 

and for ifort it is:

ifort version 2021.13.0
ifort: error #10105: /home/opt/INTEL/oneapi/compiler/2024.2/bin/../bin/fortcom: core dumped
ifort: warning #10102: unknown signal(412480896)
ifort: error #10106: Fatal error in /home/opt/INTEL/oneapi/compiler/2024.2/bin/../bin/fortcom, terminated by unknown
compilation aborted for MyModule.F90 (code 1)
0 Kudos
2 Replies
andrew_4619
Honored Contributor III
713 Views
I am thinking this is a variation of a bug that has been posted a couple of times over the last few months. Search the forum....
0 Kudos
FlyingHermes
New Contributor I
670 Views

Thanks for the feedback. I dug into the forum up to last September but could not find any similar bug. Maybe I missed it, or maybe it is older. Do you remember if this bug has been escalated to the compiler team?

0 Kudos
Reply