<?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 Re: Circular type references in Intel® Fortran Compiler</title>
    <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Circular-type-references/m-p/875181#M73617</link>
    <description>&lt;DIV style="margin:0px;"&gt;&lt;/DIV&gt;
This problem was corrected in 11.1 Update 1.&lt;BR /&gt;</description>
    <pubDate>Tue, 03 Nov 2009 15:46:34 GMT</pubDate>
    <dc:creator>Steven_L_Intel1</dc:creator>
    <dc:date>2009-11-03T15:46:34Z</dc:date>
    <item>
      <title>Circular type references</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Circular-type-references/m-p/875176#M73612</link>
      <description>The following causes an ICE with 11.1, which I have reported to premier support. But I have two follow up questions:&lt;BR /&gt;&lt;BR /&gt;- is it legitimate Fortran? The forward reference to B_type in A_type is ok because of the POINTER attribute, isn't it?&lt;BR /&gt;&lt;BR /&gt;- are there any workarounds to the ICE?&lt;BR /&gt;&lt;BR /&gt;I would have thought this sort of arrangment would have been reasonably common for data tree arrangments.&lt;BR /&gt;&lt;BR /&gt;Thanks for any advice,&lt;BR /&gt;&lt;BR /&gt;IanH&lt;BR /&gt;&lt;BR /&gt;
&lt;PRE&gt;[cpp]MODULE TestCircular&lt;BR /&gt;  IMPLICIT NONE    &lt;BR /&gt;  TYPE A_type&lt;BR /&gt;    TYPE(B_type), POINTER :: lots_of_bees(:)&lt;BR /&gt;    INTEGER d&lt;BR /&gt;  END TYPE A_type&lt;BR /&gt;  TYPE B_type&lt;BR /&gt;    TYPE(A_type), ALLOCATABLE :: some_ays(:)&lt;BR /&gt;    INTEGER d&lt;BR /&gt;  END TYPE B_type  &lt;BR /&gt;END MODULE TestCircular&lt;BR /&gt;[/cpp]&lt;/PRE&gt;</description>
      <pubDate>Tue, 23 Jun 2009 00:33:59 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Circular-type-references/m-p/875176#M73612</guid>
      <dc:creator>IanH</dc:creator>
      <dc:date>2009-06-23T00:33:59Z</dc:date>
    </item>
    <item>
      <title>Re: Circular type references</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Circular-type-references/m-p/875177#M73613</link>
      <description>&lt;DIV style="margin:0px;"&gt;&lt;/DIV&gt;
An ICE is always a bug, If the source code is unacceptable, the compiler should attempt to provide a diagnosis. With my most recent copy of ifort 11.1 beta for x86_64, I have to set -diag-enable sc, which you didn't mention, in order to provoke a compile time segmentation violation. So it does seem there is a bug, at least in that option.  Trying options -stand=f95 and -stand=f03, the compiler says you are using an extension to f95 (a warning, not a failure), but has no complaint about f03.&lt;BR /&gt;</description>
      <pubDate>Tue, 23 Jun 2009 01:18:31 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Circular-type-references/m-p/875177#M73613</guid>
      <dc:creator>TimP</dc:creator>
      <dc:date>2009-06-23T01:18:31Z</dc:date>
    </item>
    <item>
      <title>Re: Circular type references</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Circular-type-references/m-p/875178#M73614</link>
      <description>&lt;DIV style="margin:0px;"&gt;
&lt;DIV id="quote_reply" style="width: 100%; margin-top: 5px;"&gt;
&lt;DIV style="margin-left:2px;margin-right:2px;"&gt;Quoting - &lt;A href="https://community.intel.com/en-us/profile/367365"&gt;tim18&lt;/A&gt;&lt;/DIV&gt;
&lt;DIV style="background-color:#E5E5E5; padding:5px;border: 1px; border-style: inset;margin-left:2px;margin-right:2px;"&gt;&lt;EM&gt; An ICE is always a bug, If the source code is unacceptable, the compiler should attempt to provide a diagnosis. With my most recent copy of ifort 11.1 beta for x86_64, I have to set -diag-enable sc, which you didn't mention, in order to provoke a compile time segmentation violation. So it does seem there is a bug, at least in that option.  Trying options -stand=f95 and -stand=f03, the compiler says you are using an extension to f95 (a warning, not a failure), but has no complaint about f03.&lt;BR /&gt;&lt;/EM&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;BR /&gt;Thanks. What's the windows command line or IDE equivalent of the -diag-enable option you mention? F03 is my target.&lt;BR /&gt;&lt;BR /&gt;(If the option you listed was for static verification then I am not using that - at the moment I get an ICE with what is just the out-of-the-box IA32 command line build environment with 11.1 build 35, with no additional ifort command line options.)&lt;BR /&gt;&lt;BR /&gt;IanH&lt;BR /&gt;</description>
      <pubDate>Tue, 23 Jun 2009 03:16:42 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Circular-type-references/m-p/875178#M73614</guid>
      <dc:creator>IanH</dc:creator>
      <dc:date>2009-06-23T03:16:42Z</dc:date>
    </item>
    <item>
      <title>Re: Circular type references</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Circular-type-references/m-p/875179#M73615</link>
      <description>&lt;DIV style="margin: 0px; height: auto;"&gt;&lt;/DIV&gt;
I can get an ICE with no options. -diag-enable-sc is static verifier/source checker and would not create an executable if you used it.&lt;BR /&gt;&lt;BR /&gt;This code should work and I am astonished it doesn't. Thanks for reporting it. You can use 11.0.074 to compile this.&lt;BR /&gt;</description>
      <pubDate>Tue, 23 Jun 2009 12:24:06 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Circular-type-references/m-p/875179#M73615</guid>
      <dc:creator>Steven_L_Intel1</dc:creator>
      <dc:date>2009-06-23T12:24:06Z</dc:date>
    </item>
    <item>
      <title>Re: Circular type references</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Circular-type-references/m-p/875180#M73616</link>
      <description>&lt;DIV style="margin:0px;"&gt;&lt;/DIV&gt;
&lt;BR /&gt;Yes, this bug was in the compiler proper (not part of extra diagnostic checking) and has been fixed for an 11.1 update.&lt;BR /&gt;&lt;BR /&gt; - Lorri</description>
      <pubDate>Tue, 23 Jun 2009 20:03:07 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Circular-type-references/m-p/875180#M73616</guid>
      <dc:creator>Lorri_M_Intel</dc:creator>
      <dc:date>2009-06-23T20:03:07Z</dc:date>
    </item>
    <item>
      <title>Re: Circular type references</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Circular-type-references/m-p/875181#M73617</link>
      <description>&lt;DIV style="margin:0px;"&gt;&lt;/DIV&gt;
This problem was corrected in 11.1 Update 1.&lt;BR /&gt;</description>
      <pubDate>Tue, 03 Nov 2009 15:46:34 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Circular-type-references/m-p/875181#M73617</guid>
      <dc:creator>Steven_L_Intel1</dc:creator>
      <dc:date>2009-11-03T15:46:34Z</dc:date>
    </item>
  </channel>
</rss>

