https://community.intel.com/t5/Intel-Fortran-Compiler/ICE-for-use-of-symbol-that-should-be-private-from-nested-module/m-p/771345#M22717 <P>This got fixed in 13.0.</P> Tue, 27 Aug 2013 19:24:48 GMT Steven_L_Intel1 2013-08-27T19:24:48Z https://community.intel.com/t5/Intel-Fortran-Compiler/ICE-for-use-of-symbol-that-should-be-private-from-nested-module/m-p/771341#M22713 <P>Moved from unrelated thread</P> Sun, 05 Dec 2010 03:45:48 GMT https://community.intel.com/t5/Intel-Fortran-Compiler/ICE-for-use-of-symbol-that-should-be-private-from-nested-module/m-p/771341#M22713 Steven_L_Intel1 2010-12-05T03:45:48Z https://community.intel.com/t5/Intel-Fortran-Compiler/ICE-for-use-of-symbol-that-should-be-private-from-nested-module/m-p/771342#M22714 Ok - thanks for the response. I'll start abbreviating some of my module names. I think the new mangling convention is definitely safe from accidental symbol clashes! It was the repetitiion of the module name that I was curious about - I wondered whether this was a change in preparation for sub-modules.<BR /><BR />Completely unrelated - here's a snippet that ICE's 12.0. 11.1 accepts the example as it is, but probably shouldn't have. 12.0 will still ICE even if the code is corrected.<BR /><BR /><A onclick="ndownload('http://software.intel.com/file/32024')">ifort-12-ice.f90</A> Thu, 11 Nov 2010 04:05:56 GMT https://community.intel.com/t5/Intel-Fortran-Compiler/ICE-for-use-of-symbol-that-should-be-private-from-nested-module/m-p/771342#M22714 IanH 2010-11-11T04:05:56Z https://community.intel.com/t5/Intel-Fortran-Compiler/ICE-for-use-of-symbol-that-should-be-private-from-nested-module/m-p/771343#M22715 Ian,<BR /><BR />Can you provide the source that led to the repeated module name? I just want to make sure it's correct.<BR /><BR />The ICE is escalated as DPD200162880. What the compiler SHOULD do with the source you provide is generate a call to an external routine GENINTF. You are correct that version 11.1 accepts the source but it calls the wrong routine. In some ways, one might say the 12.0 behavior is an improvement, but it is still wrong. Thanks for providing this.<BR /> Thu, 11 Nov 2010 19:49:23 GMT https://community.intel.com/t5/Intel-Fortran-Compiler/ICE-for-use-of-symbol-that-should-be-private-from-nested-module/m-p/771343#M22715 Steven_L_Intel1 2010-11-11T19:49:23Z https://community.intel.com/t5/Intel-Fortran-Compiler/ICE-for-use-of-symbol-that-should-be-private-from-nested-module/m-p/771344#M22716 Amusingly, 12.0 Update 1 reverts to the 11.1 behavior - no ICE, but the wrong routine is called. Sun, 05 Dec 2010 03:52:19 GMT https://community.intel.com/t5/Intel-Fortran-Compiler/ICE-for-use-of-symbol-that-should-be-private-from-nested-module/m-p/771344#M22716 Steven_L_Intel1 2010-12-05T03:52:19Z https://community.intel.com/t5/Intel-Fortran-Compiler/ICE-for-use-of-symbol-that-should-be-private-from-nested-module/m-p/771345#M22717 <P>This got fixed in 13.0.</P> Tue, 27 Aug 2013 19:24:48 GMT https://community.intel.com/t5/Intel-Fortran-Compiler/ICE-for-use-of-symbol-that-should-be-private-from-nested-module/m-p/771345#M22717 Steven_L_Intel1 2013-08-27T19:24:48Z