<?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 Compiler crash -- segmentation violation raised in Intel® Fortran Compiler</title>
    <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Compiler-crash-segmentation-violation-raised/m-p/755291#M10778</link>
    <description>The END SUBROUTINE is also missing, but if I add that I can reproduce the problem. Thanks - I will escalate this to development. Issue ID is DPD200169285.&lt;BR /&gt;&lt;BR /&gt;I found that the use of the subroutine was not required - even putting the common at the top level of the module triggered the error. Might you be able to use an ALLOCATABLE array in the module and an ATTRIBUTES ALIGN on that? You would need to allocate it at the start of the program but otherwise it should not require code changes.</description>
    <pubDate>Mon, 09 May 2011 16:03:28 GMT</pubDate>
    <dc:creator>Steven_L_Intel1</dc:creator>
    <dc:date>2011-05-09T16:03:28Z</dc:date>
    <item>
      <title>Compiler crash -- segmentation violation raised</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Compiler-crash-segmentation-violation-raised/m-p/755289#M10776</link>
      <description>Compilation on the following code fails:&lt;BR /&gt;&lt;BR /&gt;&lt;PRE&gt;[bash]      Module ModA
        Public
      Contains
        Subroutine ModA_Sub()
        Integer(4) :: dummy

!DEC$   ATTRIBUTES ALIGN: 4096 :: CBLK
        Common/CBLK/ dummy
      End Module ModA

      Program CrashProgram
      Use ModA
      Call ModA_Sub()
      end Program CrashProgram[/bash]&lt;/PRE&gt; &lt;BR /&gt;Compile with "ifort -extend-source 132 -assume nounderscore -assume nobscc -align dcommons -static-libgcc -zero -fp-port -save -c -fpe0 -ftz -prec-div -fp-stack-check -ccdefault fortran -traceback -fp-model precise -xSSE2 -axSSE2 -g -debug full -debug-parameters -check bounds -O0 -m32 Crash.for"&lt;BR /&gt;&lt;BR /&gt;"Crash.for: catastrophic error: **Internal compiler error: segmentation 
violation signal raised** Please report this error along with the 
circumstances in whcih it occurred in a Software Problem Report. Note: 
File and line given may not be explicit cause of this error."&lt;BR /&gt;&lt;BR /&gt;Removing the page-align directive eliminates the crash.&lt;BR /&gt;&lt;BR /&gt;Intel Fortran Compiler XE for applications running on IA-32, Version 12.0.1.107 Build 20101116</description>
      <pubDate>Mon, 09 May 2011 15:39:42 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Compiler-crash-segmentation-violation-raised/m-p/755289#M10776</guid>
      <dc:creator>ereisch</dc:creator>
      <dc:date>2011-05-09T15:39:42Z</dc:date>
    </item>
    <item>
      <title>Compiler crash -- segmentation violation raised</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Compiler-crash-segmentation-violation-raised/m-p/755290#M10777</link>
      <description>For some reason, the syntax highlighter removed the first part of Line 7. It should read:&lt;BR /&gt;&lt;BR /&gt;!DEC$ ATTRIBUTES ALIGN: 4096 :: CBLK</description>
      <pubDate>Mon, 09 May 2011 15:41:35 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Compiler-crash-segmentation-violation-raised/m-p/755290#M10777</guid>
      <dc:creator>ereisch</dc:creator>
      <dc:date>2011-05-09T15:41:35Z</dc:date>
    </item>
    <item>
      <title>Compiler crash -- segmentation violation raised</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Compiler-crash-segmentation-violation-raised/m-p/755291#M10778</link>
      <description>The END SUBROUTINE is also missing, but if I add that I can reproduce the problem. Thanks - I will escalate this to development. Issue ID is DPD200169285.&lt;BR /&gt;&lt;BR /&gt;I found that the use of the subroutine was not required - even putting the common at the top level of the module triggered the error. Might you be able to use an ALLOCATABLE array in the module and an ATTRIBUTES ALIGN on that? You would need to allocate it at the start of the program but otherwise it should not require code changes.</description>
      <pubDate>Mon, 09 May 2011 16:03:28 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Compiler-crash-segmentation-violation-raised/m-p/755291#M10778</guid>
      <dc:creator>Steven_L_Intel1</dc:creator>
      <dc:date>2011-05-09T16:03:28Z</dc:date>
    </item>
    <item>
      <title>Compiler crash -- segmentation violation raised</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Compiler-crash-segmentation-violation-raised/m-p/755292#M10779</link>
      <description>The syntax highlighter did not remove the first part; if you choose "view plain" you will see that the line is intact.&lt;BR /&gt;&lt;BR /&gt;I agree that it is annoying that the line gets mangled when seen in the browser. Similarly, leading blanks in the first line of code added using the syntax highlighter are not shown. I wish Intel would show us at least a work-around to avoid such problems (what-you-see-is-not-what-you-have and vice versa).</description>
      <pubDate>Mon, 09 May 2011 16:20:42 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Compiler-crash-segmentation-violation-raised/m-p/755292#M10779</guid>
      <dc:creator>mecej4</dc:creator>
      <dc:date>2011-05-09T16:20:42Z</dc:date>
    </item>
    <item>
      <title>Compiler crash -- segmentation violation raised</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Compiler-crash-segmentation-violation-raised/m-p/755293#M10780</link>
      <description>I know the syntax highlighter has issues. We're using an open source module for this with Fortran-specific definitions I provided. I don't understand why it corrupts lines sometimes. It is being worked on.</description>
      <pubDate>Mon, 09 May 2011 16:26:02 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Compiler-crash-segmentation-violation-raised/m-p/755293#M10780</guid>
      <dc:creator>Steven_L_Intel1</dc:creator>
      <dc:date>2011-05-09T16:26:02Z</dc:date>
    </item>
    <item>
      <title>Compiler crash -- segmentation violation raised</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Compiler-crash-segmentation-violation-raised/m-p/755294#M10781</link>
      <description>The internal compiler error has been fixed for an update later this year. However, the ALIGN directive will be ignored for a COMMON in a module. A future version will enable that feature.</description>
      <pubDate>Tue, 26 Jul 2011 19:37:26 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Compiler-crash-segmentation-violation-raised/m-p/755294#M10781</guid>
      <dc:creator>Steven_L_Intel1</dc:creator>
      <dc:date>2011-07-26T19:37:26Z</dc:date>
    </item>
    <item>
      <title>The "future version" will be</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Compiler-crash-segmentation-violation-raised/m-p/755295#M10782</link>
      <description>&lt;P&gt;The "future version" will be released later this year.&lt;/P&gt;</description>
      <pubDate>Wed, 27 Mar 2013 19:30:21 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Compiler-crash-segmentation-violation-raised/m-p/755295#M10782</guid>
      <dc:creator>Steven_L_Intel1</dc:creator>
      <dc:date>2013-03-27T19:30:21Z</dc:date>
    </item>
  </channel>
</rss>

