<?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: debugging output generated by ifx in Intel® Fortran Compiler</title>
    <link>https://community.intel.com/t5/Intel-Fortran-Compiler/debugging-output-generated-by-ifx/m-p/1583990#M171425</link>
    <description>&lt;P&gt;ifx uses LLVM memory sanitizer features to check for uninitialized variables. That output can be confusing. Ron posted &lt;A href="https://community.intel.com/t5/Intel-Fortran-Compiler/Known-bug-with-check-all-or-check-uninit-in-ifx-2024-0-0-for/m-p/1545825#M169267" target="_blank" rel="noopener"&gt;this message&lt;/A&gt; about it.&lt;/P&gt;
&lt;P&gt;ifx 2024.1.0 will be available in the next week or so.&lt;/P&gt;
&lt;P&gt;Also, with ifx -check uninit examines scalars, arrays, array slices, array elements, allocatable, automatics, and derived types.&amp;nbsp;By contrast, ifort could only catch local scalar variables of intrinsic type INTEGER, REAL, COMPLEX, and LOGICAL without the SAVE attribute.&lt;/P&gt;
&lt;P&gt;One other point... this feature is only enabled on Linux.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 27 Mar 2024 18:48:37 GMT</pubDate>
    <dc:creator>Barbara_P_Intel</dc:creator>
    <dc:date>2024-03-27T18:48:37Z</dc:date>
    <item>
      <title>debugging output generated by ifx</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/debugging-output-generated-by-ifx/m-p/1578176#M171399</link>
      <description>&lt;P class=""&gt;&lt;SPAN class=""&gt;Having worked with ifort based oneAPI for several years,&lt;/SPAN&gt;&lt;SPAN class=""&gt;&amp;nbsp;for debugging the code I have used the flags&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;safe: FC_ALL += -check all -traceback -fstack-protector -assume protect_parens -implicitnone -warn all,noexternal -fpe-all=0&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN class=""&gt;safe: CC_ALL += -traceback -fstack-protector&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;which gave a clear traceback of the error module-by-module, up to the line where the fault occurred.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;However, with the new ifx-based oneAPI, the same compilation flags produce an incomprehensible output.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;How can I recover the simpler and clearer debugging output I use to get from ifort?&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;Thanks.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 06 Mar 2024 12:54:34 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/debugging-output-generated-by-ifx/m-p/1578176#M171399</guid>
      <dc:creator>lrego-developer</dc:creator>
      <dc:date>2024-03-06T12:54:34Z</dc:date>
    </item>
    <item>
      <title>Re: debugging output generated by ifx</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/debugging-output-generated-by-ifx/m-p/1583990#M171425</link>
      <description>&lt;P&gt;ifx uses LLVM memory sanitizer features to check for uninitialized variables. That output can be confusing. Ron posted &lt;A href="https://community.intel.com/t5/Intel-Fortran-Compiler/Known-bug-with-check-all-or-check-uninit-in-ifx-2024-0-0-for/m-p/1545825#M169267" target="_blank" rel="noopener"&gt;this message&lt;/A&gt; about it.&lt;/P&gt;
&lt;P&gt;ifx 2024.1.0 will be available in the next week or so.&lt;/P&gt;
&lt;P&gt;Also, with ifx -check uninit examines scalars, arrays, array slices, array elements, allocatable, automatics, and derived types.&amp;nbsp;By contrast, ifort could only catch local scalar variables of intrinsic type INTEGER, REAL, COMPLEX, and LOGICAL without the SAVE attribute.&lt;/P&gt;
&lt;P&gt;One other point... this feature is only enabled on Linux.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 27 Mar 2024 18:48:37 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/debugging-output-generated-by-ifx/m-p/1583990#M171425</guid>
      <dc:creator>Barbara_P_Intel</dc:creator>
      <dc:date>2024-03-27T18:48:37Z</dc:date>
    </item>
    <item>
      <title>Re: debugging output generated by ifx</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/debugging-output-generated-by-ifx/m-p/1585257#M171500</link>
      <description>&lt;P&gt;Hello there,&lt;/P&gt;&lt;P&gt;I have the following problem whenever I try to use ifx-based oneAPI toolkit to debug my code with the safe flags below&lt;/P&gt;&lt;P&gt;-g -check all,nouninit -traceback -fstack-protector -assume protect_parens -implicitnone -warn all,noexternal -fpe-all=0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The output produced by some fatal error (also featured in the attached image) is incomprehensible to me; it looks like&lt;/P&gt;&lt;P&gt;ifx: warning #10182: disabling optimization; runtime debug checks enabled&lt;BR /&gt;ld: EnvField.o: in function `PC_implicit_mapper':&lt;BR /&gt;ifxKE5Z2y.i:(.text+0x184f7): undefined reference to `__tgt_mapper_num_components'&lt;BR /&gt;ld: ifxKE5Z2y.i:(.text+0x1852f): undefined reference to `__tgt_push_mapper_component'&lt;BR /&gt;ld: ifxKE5Z2y.i:(.text+0x18565): undefined reference to `__tgt_mapper_num_components'&lt;BR /&gt;ld: ifxKE5Z2y.i:(.text+0x1859a): undefined reference to `__tgt_push_mapper_component'&lt;BR /&gt;ld: ifxKE5Z2y.i:(.text+0x186e3): undefined reference to `__tgt_push_mapper_component'&lt;BR /&gt;ld: ifxKE5Z2y.i:(.text+0x1874f): undefined reference to `__tgt_push_mapper_component'&lt;BR /&gt;ld: ifxKE5Z2y.i:(.text+0x188b1): undefined reference to `__tgt_push_mapper_component'&lt;BR /&gt;ld: ifxKE5Z2y.i:(.text+0x1891d): undefined reference to `__tgt_push_mapper_component'&lt;BR /&gt;ld: EnvField.o:ifxKE5Z2y.i:(.text+0x18a95): more undefined references to `__tgt_push_mapper_component' follow&lt;BR /&gt;ld: EnvField.o: in function `ATOM_implicit_mapper':&lt;BR /&gt;ifxKE5Z2y.i:(.text+0x18c5c): undefined reference to `__tgt_mapper_num_components'&lt;BR /&gt;ld: ifxKE5Z2y.i:(.text+0x18ca0): undefined reference to `__tgt_push_mapper_component'&lt;BR /&gt;ld: ifxKE5Z2y.i:(.text+0x18cd6): undefined reference to `__tgt_mapper_num_components'&lt;BR /&gt;ld: ifxKE5Z2y.i:(.text+0x18d0e): undefined reference to `__tgt_push_mapper_component'&lt;BR /&gt;ld: ifxKE5Z2y.i:(.text+0x18e1b): undefined reference to `__tgt_push_mapper_component'&lt;BR /&gt;ld: ifxKE5Z2y.i:(.text+0x18f2c): undefined reference to `__tgt_push_mapper_component'&lt;BR /&gt;ld: ifxKE5Z2y.i:(.text+0x1903d): undefined reference to `__tgt_push_mapper_component'&lt;BR /&gt;ld: ifxKE5Z2y.i:(.text+0x1914e): undefined reference to `__tgt_push_mapper_component'&lt;BR /&gt;ld: EnvField.o:ifxKE5Z2y.i:(.text+0x1925f): more undefined references to `__tgt_push_mapper_component' follow&lt;BR /&gt;ld: EnvField.o: in function `QNCA_a0$TYPE_M$.btMOLECULAR*$rank1$_implicit_mapper':&lt;BR /&gt;ifxKE5Z2y.i:(.text+0x1a854): undefined reference to `__tgt_mapper_num_components'&lt;BR /&gt;ld: ifxKE5Z2y.i:(.text+0x1a88c): undefined reference to `__tgt_push_mapper_component'&lt;BR /&gt;ld: ifxKE5Z2y.i:(.text+0x1aaed): undefined reference to `__tgt_push_mapper_component'&lt;BR /&gt;ld: ifxKE5Z2y.i:(.text+0x1ab5b): undefined reference to `__tgt_push_mapper_component'&lt;BR /&gt;ld: ifxKE5Z2y.i:(.text+0x1acc6): undefined reference to `__tgt_push_mapper_component'&lt;BR /&gt;ld: ifxKE5Z2y.i:(.text+0x1adda): undefined reference to `__tgt_push_mapper_component'&lt;BR /&gt;ld: EnvField.o:ifxKE5Z2y.i:(.text+0x1aeee): more undefined references to `__tgt_push_mapper_component' follow&lt;BR /&gt;make: *** [makefile:222: dynemol] Error 1&lt;/P&gt;</description>
      <pubDate>Mon, 01 Apr 2024 21:00:37 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/debugging-output-generated-by-ifx/m-p/1585257#M171500</guid>
      <dc:creator>lrego-developer</dc:creator>
      <dc:date>2024-04-01T21:00:37Z</dc:date>
    </item>
    <item>
      <title>Re: debugging output generated by ifx</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/debugging-output-generated-by-ifx/m-p/1585272#M171501</link>
      <description>&lt;P&gt;Can you please provide a small reproducer?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 01 Apr 2024 22:24:17 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/debugging-output-generated-by-ifx/m-p/1585272#M171501</guid>
      <dc:creator>Barbara_P_Intel</dc:creator>
      <dc:date>2024-04-01T22:24:17Z</dc:date>
    </item>
    <item>
      <title>Re: debugging output generated by ifx</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/debugging-output-generated-by-ifx/m-p/1651222#M174676</link>
      <description>&lt;P&gt;I get a similar output when I try linking code that was compiled in debug mode with code that was compiled with some optimisations. This works fine with ifort, but not with ifx.&lt;/P&gt;&lt;P&gt;Unfortunately, this only happens on our rather larger code base, but not for the minimal examples I tried.&lt;/P&gt;&lt;P&gt;Compiling and running the code base completely either in debug or optimized mode works fine.&lt;/P&gt;</description>
      <pubDate>Fri, 20 Dec 2024 16:12:29 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/debugging-output-generated-by-ifx/m-p/1651222#M174676</guid>
      <dc:creator>TilPiffl</dc:creator>
      <dc:date>2024-12-20T16:12:29Z</dc:date>
    </item>
    <item>
      <title>Re: debugging output generated by ifx</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/debugging-output-generated-by-ifx/m-p/1651243#M174677</link>
      <description>&lt;P&gt;We have some issues with Od that will be fixed in the next release. This means similar reports are already in the system and have been fixed. Hopefully, this will also cover your use case.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 20 Dec 2024 18:43:58 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/debugging-output-generated-by-ifx/m-p/1651243#M174677</guid>
      <dc:creator>Devorah_H_Intel</dc:creator>
      <dc:date>2024-12-20T18:43:58Z</dc:date>
    </item>
  </channel>
</rss>

