<?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 Intel ifx compiler build failure with link-time (IPO) optimizations in Intel® Fortran Compiler</title>
    <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Intel-ifx-compiler-build-failure-with-link-time-IPO/m-p/1726772#M177680</link>
    <description>&lt;P&gt;I have a library that is configured with CMake. During the configuration phase, CMake's test (via&amp;nbsp;check_ipo_supported) for IPO optimization support of ifx fails, stating that the compiler (ifx) does not support IPO optimization. If I enforce IPO explicitly with ifx compiler flags, I get the following LLVM errors during the linking phase:&lt;/P&gt;&lt;LI-CODE lang="bash"&gt;ld: /tmp/lto-llvm-ecd5af.o:(.rodata.strlit.1.llvm.0+0x0): multiple definition of `strlit.1.llvm.0'; /tmp/lto-llvm-6a50da.o:(.rodata.strlit.1.llvm.0+0x0): first defined here
ld: /tmp/lto-llvm-bd59f7.o:(.rodata.str1.16+0x30): multiple definition of `strlit.16.llvm.0'; /tmp/lto-llvm-58bd2a.o:(.rodata.strlit.16.llvm.0+0x0): first defined here
ld: /tmp/lto-llvm-e20798.o:(.rodata.strlit.1.llvm.0+0x0): multiple definition of `strlit.1.llvm.0'; /tmp/lto-llvm-6a50da.o:(.rodata.strlit.1.llvm.0+0x0): first defined here
ld: /tmp/lto-llvm-e20798.o:(.rodata.strlit.llvm.0+0x0): multiple definition of `strlit.llvm.0'; /tmp/lto-llvm-281b67.o:(.rodata.strlit.llvm.0+0x0): first defined here
ld: /tmp/lto-llvm-8a56ed.o:(.rodata.strlit.1.llvm.0+0x0): multiple definition of `strlit.1.llvm.0'; /tmp/lto-llvm-6a50da.o:(.rodata.strlit.1.llvm.0+0x0): first defined here
ld: /tmp/lto-llvm-bc72e5.o:(.rodata.strlit.6.llvm.0+0x0): multiple definition of `strlit.6.llvm.0'; /tmp/lto-llvm-8a56ed.o:(.rodata.strlit.6.llvm.0+0x0): first defined here
ld: /tmp/lto-llvm-bc72e5.o:(.rodata.strlit.5.llvm.0+0x0): multiple definition of `strlit.5.llvm.0'; /tmp/lto-llvm-8a56ed.o:(.rodata.strlit.5.llvm.0+0x0): first defined here
ld: /tmp/lto-llvm-f75a37.o:(.rodata.strlit.17.llvm.0+0x0): multiple definition of `strlit.17.llvm.0'; /tmp/lto-llvm-58bd2a.o:(.rodata.strlit.17.llvm.0+0x0): first defined here
ld: /tmp/lto-llvm-f75a37.o:(.rodata.strlit.22.llvm.0+0x0): multiple definition of `strlit.22.llvm.0'; /tmp/lto-llvm-58bd2a.o:(.rodata.cst4+0x14): first defined here
ld: /tmp/lto-llvm-f75a37.o:(.rodata.strlit.1.llvm.0+0x0): multiple definition of `strlit.1.llvm.0'; /tmp/lto-llvm-6a50da.o:(.rodata.strlit.1.llvm.0+0x0): first defined here&lt;/LI-CODE&gt;&lt;P&gt;Any ideas why such an error may be happening?&lt;BR /&gt;&lt;BR /&gt;The IFX compiler flags explicitly passed are the following:&lt;/P&gt;&lt;LI-CODE lang="bash"&gt;-O3 -fPIC -nologo -threads -standard-semantics -integer-size 32 -static-intel -unroll -finline-functions -ftz -inline-forceinline -flto=thin -heap-arrays&lt;/LI-CODE&gt;&lt;P&gt;The IFX linker flags explicitly passed are the following:&lt;/P&gt;&lt;LI-CODE lang="bash"&gt;-fPIC -O3 -nologo -threads -standard-semantics -integer-size 32 -diag-disable=7025 -diag-disable=5268 -diag-disable=10346 -diag-disable=10448 -static-intel -O3 -unroll -diag-disable=10397 -finline-functions -ftz -qopt-report=2 -inline-forceinline -flto=thin -fpic -shared -qopenmp-link=static -static -static-libstdc++ -static-libgcc -shared -nofor-main&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 18 Nov 2025 06:02:40 GMT</pubDate>
    <dc:creator>DataScientist</dc:creator>
    <dc:date>2025-11-18T06:02:40Z</dc:date>
    <item>
      <title>Intel ifx compiler build failure with link-time (IPO) optimizations</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Intel-ifx-compiler-build-failure-with-link-time-IPO/m-p/1726772#M177680</link>
      <description>&lt;P&gt;I have a library that is configured with CMake. During the configuration phase, CMake's test (via&amp;nbsp;check_ipo_supported) for IPO optimization support of ifx fails, stating that the compiler (ifx) does not support IPO optimization. If I enforce IPO explicitly with ifx compiler flags, I get the following LLVM errors during the linking phase:&lt;/P&gt;&lt;LI-CODE lang="bash"&gt;ld: /tmp/lto-llvm-ecd5af.o:(.rodata.strlit.1.llvm.0+0x0): multiple definition of `strlit.1.llvm.0'; /tmp/lto-llvm-6a50da.o:(.rodata.strlit.1.llvm.0+0x0): first defined here
ld: /tmp/lto-llvm-bd59f7.o:(.rodata.str1.16+0x30): multiple definition of `strlit.16.llvm.0'; /tmp/lto-llvm-58bd2a.o:(.rodata.strlit.16.llvm.0+0x0): first defined here
ld: /tmp/lto-llvm-e20798.o:(.rodata.strlit.1.llvm.0+0x0): multiple definition of `strlit.1.llvm.0'; /tmp/lto-llvm-6a50da.o:(.rodata.strlit.1.llvm.0+0x0): first defined here
ld: /tmp/lto-llvm-e20798.o:(.rodata.strlit.llvm.0+0x0): multiple definition of `strlit.llvm.0'; /tmp/lto-llvm-281b67.o:(.rodata.strlit.llvm.0+0x0): first defined here
ld: /tmp/lto-llvm-8a56ed.o:(.rodata.strlit.1.llvm.0+0x0): multiple definition of `strlit.1.llvm.0'; /tmp/lto-llvm-6a50da.o:(.rodata.strlit.1.llvm.0+0x0): first defined here
ld: /tmp/lto-llvm-bc72e5.o:(.rodata.strlit.6.llvm.0+0x0): multiple definition of `strlit.6.llvm.0'; /tmp/lto-llvm-8a56ed.o:(.rodata.strlit.6.llvm.0+0x0): first defined here
ld: /tmp/lto-llvm-bc72e5.o:(.rodata.strlit.5.llvm.0+0x0): multiple definition of `strlit.5.llvm.0'; /tmp/lto-llvm-8a56ed.o:(.rodata.strlit.5.llvm.0+0x0): first defined here
ld: /tmp/lto-llvm-f75a37.o:(.rodata.strlit.17.llvm.0+0x0): multiple definition of `strlit.17.llvm.0'; /tmp/lto-llvm-58bd2a.o:(.rodata.strlit.17.llvm.0+0x0): first defined here
ld: /tmp/lto-llvm-f75a37.o:(.rodata.strlit.22.llvm.0+0x0): multiple definition of `strlit.22.llvm.0'; /tmp/lto-llvm-58bd2a.o:(.rodata.cst4+0x14): first defined here
ld: /tmp/lto-llvm-f75a37.o:(.rodata.strlit.1.llvm.0+0x0): multiple definition of `strlit.1.llvm.0'; /tmp/lto-llvm-6a50da.o:(.rodata.strlit.1.llvm.0+0x0): first defined here&lt;/LI-CODE&gt;&lt;P&gt;Any ideas why such an error may be happening?&lt;BR /&gt;&lt;BR /&gt;The IFX compiler flags explicitly passed are the following:&lt;/P&gt;&lt;LI-CODE lang="bash"&gt;-O3 -fPIC -nologo -threads -standard-semantics -integer-size 32 -static-intel -unroll -finline-functions -ftz -inline-forceinline -flto=thin -heap-arrays&lt;/LI-CODE&gt;&lt;P&gt;The IFX linker flags explicitly passed are the following:&lt;/P&gt;&lt;LI-CODE lang="bash"&gt;-fPIC -O3 -nologo -threads -standard-semantics -integer-size 32 -diag-disable=7025 -diag-disable=5268 -diag-disable=10346 -diag-disable=10448 -static-intel -O3 -unroll -diag-disable=10397 -finline-functions -ftz -qopt-report=2 -inline-forceinline -flto=thin -fpic -shared -qopenmp-link=static -static -static-libstdc++ -static-libgcc -shared -nofor-main&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 18 Nov 2025 06:02:40 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Intel-ifx-compiler-build-failure-with-link-time-IPO/m-p/1726772#M177680</guid>
      <dc:creator>DataScientist</dc:creator>
      <dc:date>2025-11-18T06:02:40Z</dc:date>
    </item>
    <item>
      <title>Re: Intel ifx compiler build failure with link-time (IPO) optimizations</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Intel-ifx-compiler-build-failure-with-link-time-IPO/m-p/1726819#M177686</link>
      <description>&lt;P&gt;After extensive investigation, it turns out that passing the `--allow-multiple-definition` flag to the linker resolves&amp;nbsp;the issue. But I consider it only a temporary solution. I still appreciate any permanent fix to the above compilation error. The platform is Microsoft WSL Ubuntu.&lt;/P&gt;</description>
      <pubDate>Tue, 18 Nov 2025 16:38:06 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Intel-ifx-compiler-build-failure-with-link-time-IPO/m-p/1726819#M177686</guid>
      <dc:creator>DataScientist</dc:creator>
      <dc:date>2025-11-18T16:38:06Z</dc:date>
    </item>
    <item>
      <title>Re: Intel ifx compiler build failure with link-time (IPO) optimizations</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Intel-ifx-compiler-build-failure-with-link-time-IPO/m-p/1727180#M177709</link>
      <description>&lt;P&gt;Do you have a small reproducer showing this problem?&lt;/P&gt;</description>
      <pubDate>Thu, 20 Nov 2025 18:58:51 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Intel-ifx-compiler-build-failure-with-link-time-IPO/m-p/1727180#M177709</guid>
      <dc:creator>Igor_V_Intel</dc:creator>
      <dc:date>2025-11-20T18:58:51Z</dc:date>
    </item>
    <item>
      <title>Re: Intel ifx compiler build failure with link-time (IPO) optimizations</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Intel-ifx-compiler-build-failure-with-link-time-IPO/m-p/1729613#M177838</link>
      <description>&lt;P&gt;Unfortunately, I do not have a minimal reproducible example yet. The flag I mentioned above (`--allow-multiple-definition`) has temporarily bypassed the issue, although I suppose that is not a permanent solution. I will work on a minimal reproducer to share here as soon as other obligations allow.&lt;/P&gt;</description>
      <pubDate>Wed, 10 Dec 2025 03:14:41 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Intel-ifx-compiler-build-failure-with-link-time-IPO/m-p/1729613#M177838</guid>
      <dc:creator>DataScientist</dc:creator>
      <dc:date>2025-12-10T03:14:41Z</dc:date>
    </item>
  </channel>
</rss>

