<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in cross-mingw</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>ab5ac1ad - config/x86: fix MinGW cross build with Meson 0.49</title>
        <link>http://172.16.0.5:8080/history/dpdk/config/x86/cross-mingw#ab5ac1ad</link>
        <description>config/x86: fix MinGW cross build with Meson 0.49Cross build with MinGW was broken for the baseline meson 0.49.2.Cause: in c_args = &apos;-mno-avx512f&apos; from config/x86/cross-mingw,each character was treated as a separate compiler option:    meson.build:4:0: ERROR:  Compiler x86_64-w64-mingw32-gcc can not compile programs.With c_args = [&apos;-mno-avx512f&apos;] configuration passed, but build failed,because Meson placed -mno-avx512f after -mavx512f in CFLAGS:    In file included from /usr/lib/gcc/x86_64-w64-mingw32/9.3-win32/include/immintrin.h:55,                     from /usr/lib/gcc/x86_64-w64-mingw32/9.3-win32/include/x86intrin.h:32,                     from ../dpdk/lib/net/net_crc_avx512.c:13:    /usr/lib/gcc/x86_64-w64-mingw32/9.3-win32/include/avx512fintrin.h:1650:1:            error: inlining failed in call to always_inline _mm512_ternarylogic_epi64:            target specific option mismatch     1650 | _mm512_ternarylogic_epi64 (__m512i __A, __m512i __B, __m512i __C,          | ^~~~~~~~~~~~~~~~~~~~~~~~~    ../dpdk/lib/net/net_crc_avx512.c:59:9: note: called from here       59 |  return _mm512_ternarylogic_epi64(tmp0, tmp1, data_block, 0x96);          |         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Additionally, -m[no-]avx512f flag is expected to be in machine_argsby all the checks in meson.build files.Commit 419c6e9af69e (&quot;net/i40e: fix build for Windows MinGW&quot;)fixed the errors cause by MinGW using AVX512F on Windows.The binutils AVX512F bug check is now portable,so enable it for Windows to switch AVX512 support on and offwithout any special logic for MinGW.Fixes: 549bfc83168f (&quot;config: disable AVX512 with MinGW&quot;)Signed-off-by: Dmitry Kozlyuk &lt;dmitry.kozliuk@gmail.com&gt;Acked-by: Bruce Richardson &lt;bruce.richardson@intel.com&gt;

            List of files:
            /dpdk/config/x86/cross-mingw</description>
        <pubDate>Fri, 12 Nov 2021 21:48:26 +0000</pubDate>
        <dc:creator>Dmitry Kozlyuk &lt;dmitry.kozliuk@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>549bfc83 - config: disable AVX512 with MinGW</title>
        <link>http://172.16.0.5:8080/history/dpdk/config/x86/cross-mingw#549bfc83</link>
        <description>config: disable AVX512 with MinGWDisable AVX512 when on MinGW cross build, as .seh_savexmmbuild error reports if AVX512 is enabled:	Error: invalid register for .seh_savexmmSigned-off-by: Leyi Rong &lt;leyi.rong@intel.com&gt;Tested-by: Pallavi Kadam &lt;pallavi.kadam@intel.com&gt;Tested-by: David Marchand &lt;david.marchand@redhat.com&gt;

            List of files:
            /dpdk/config/x86/cross-mingw</description>
        <pubDate>Wed, 27 Jan 2021 14:27:05 +0000</pubDate>
        <dc:creator>Leyi Rong &lt;leyi.rong@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>3b643139 - devtools: add Windows cross-build test with MinGW</title>
        <link>http://172.16.0.5:8080/history/dpdk/config/x86/cross-mingw#3b643139</link>
        <description>devtools: add Windows cross-build test with MinGWThe Meson cross file is renamed from meson_mingw.txt to cross-mingw,and is added to test-meson-builds.sh.The only example supported on Windows so far is &quot;helloworld&quot;,that&apos;s why the default list of examples is overridden.Signed-off-by: Thomas Monjalon &lt;thomas@monjalon.net&gt;

            List of files:
            /dpdk/config/x86/cross-mingw</description>
        <pubDate>Sun, 14 Jun 2020 21:58:45 +0000</pubDate>
        <dc:creator>Thomas Monjalon &lt;thomas@monjalon.net&gt;</dc:creator>
    </item>
</channel>
</rss>
