<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic ICE when associated is called for a dummy (function) procedure pointer in Intel® Fortran Compiler</title>
    <link>https://community.intel.com/t5/Intel-Fortran-Compiler/ICE-when-associated-is-called-for-a-dummy-function-procedure/m-p/766744#M20508</link>
    <description>I'm using&lt;BR /&gt;&lt;BR /&gt;$ uname -a&lt;BR /&gt;Linux stonehenge 3.3.0-4.fc16.x86_64 #1 SMP Tue Mar 20 18:05:40 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux&lt;BR /&gt;&lt;BR /&gt;$ ifort -V&lt;BR /&gt;Intel Fortran Intel 64 Compiler XE for applications running on Intel 64, Version 12.1 Build 20120212&lt;BR /&gt;&lt;BR /&gt;and have&lt;BR /&gt;&lt;BR /&gt;$ cat pp.f90&lt;BR /&gt;[fortran]module m0
abstract interface
  function f()
  end function f
end interface
interface
  subroutine s(ff)
    import f
    procedure(f), pointer, intent(in) :: ff
  end subroutine s
end interface
end module m0
use m0, only : f, s
procedure(f) :: f2
procedure(f), pointer :: pp
pp =&amp;gt; f2
call s(pp)
end
subroutine s(ff)
  use m0, only : f
  procedure(f), pointer, intent(in) :: ff
  procedure(f) :: f2
  print *, associated(ff,f2)
end subroutine s
function f2()
end function f2
[/fortran] &lt;BR /&gt;which gives&lt;BR /&gt;&lt;BR /&gt;$ ifort pp.f90&lt;BR /&gt;pp.f90: catastrophic error: **Internal compiler error: segmentation violation signal raised** Please report this error along with the circumstances in which it occurred in a Software Problem Report. Note: File and line given may not be explicit cause of this error.&lt;BR /&gt;compilation aborted for pp.f90 (code 1)&lt;BR /&gt;&lt;BR /&gt;The file compiles OK if f, ff and f2 are subroutines.&lt;BR /&gt;</description>
    <pubDate>Wed, 28 Mar 2012 10:49:14 GMT</pubDate>
    <dc:creator>Cross__Mat</dc:creator>
    <dc:date>2012-03-28T10:49:14Z</dc:date>
    <item>
      <title>ICE when associated is called for a dummy (function) procedure pointer</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/ICE-when-associated-is-called-for-a-dummy-function-procedure/m-p/766744#M20508</link>
      <description>I'm using&lt;BR /&gt;&lt;BR /&gt;$ uname -a&lt;BR /&gt;Linux stonehenge 3.3.0-4.fc16.x86_64 #1 SMP Tue Mar 20 18:05:40 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux&lt;BR /&gt;&lt;BR /&gt;$ ifort -V&lt;BR /&gt;Intel Fortran Intel 64 Compiler XE for applications running on Intel 64, Version 12.1 Build 20120212&lt;BR /&gt;&lt;BR /&gt;and have&lt;BR /&gt;&lt;BR /&gt;$ cat pp.f90&lt;BR /&gt;[fortran]module m0
abstract interface
  function f()
  end function f
end interface
interface
  subroutine s(ff)
    import f
    procedure(f), pointer, intent(in) :: ff
  end subroutine s
end interface
end module m0
use m0, only : f, s
procedure(f) :: f2
procedure(f), pointer :: pp
pp =&amp;gt; f2
call s(pp)
end
subroutine s(ff)
  use m0, only : f
  procedure(f), pointer, intent(in) :: ff
  procedure(f) :: f2
  print *, associated(ff,f2)
end subroutine s
function f2()
end function f2
[/fortran] &lt;BR /&gt;which gives&lt;BR /&gt;&lt;BR /&gt;$ ifort pp.f90&lt;BR /&gt;pp.f90: catastrophic error: **Internal compiler error: segmentation violation signal raised** Please report this error along with the circumstances in which it occurred in a Software Problem Report. Note: File and line given may not be explicit cause of this error.&lt;BR /&gt;compilation aborted for pp.f90 (code 1)&lt;BR /&gt;&lt;BR /&gt;The file compiles OK if f, ff and f2 are subroutines.&lt;BR /&gt;</description>
      <pubDate>Wed, 28 Mar 2012 10:49:14 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/ICE-when-associated-is-called-for-a-dummy-function-procedure/m-p/766744#M20508</guid>
      <dc:creator>Cross__Mat</dc:creator>
      <dc:date>2012-03-28T10:49:14Z</dc:date>
    </item>
    <item>
      <title>ICE when associated is called for a dummy (function) procedure</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/ICE-when-associated-is-called-for-a-dummy-function-procedure/m-p/766745#M20509</link>
      <description>Thanks for the nice test case. I can reproduce this and have escalated it as issue DPD200180573.</description>
      <pubDate>Wed, 28 Mar 2012 14:24:07 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/ICE-when-associated-is-called-for-a-dummy-function-procedure/m-p/766745#M20509</guid>
      <dc:creator>Steven_L_Intel1</dc:creator>
      <dc:date>2012-03-28T14:24:07Z</dc:date>
    </item>
    <item>
      <title>ICE when associated is called for a dummy (function) procedure</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/ICE-when-associated-is-called-for-a-dummy-function-procedure/m-p/766746#M20510</link>
      <description>This problem has been fixed for a release later this year.</description>
      <pubDate>Mon, 02 Apr 2012 13:19:13 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/ICE-when-associated-is-called-for-a-dummy-function-procedure/m-p/766746#M20510</guid>
      <dc:creator>Steven_L_Intel1</dc:creator>
      <dc:date>2012-04-02T13:19:13Z</dc:date>
    </item>
  </channel>
</rss>

