From: Thomas Monjalon <thomas@monjalon.net>
To: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Cc: dev@dpdk.org, bruce.richardson@intel.com
Subject: Re: [PATCH 0/3] config/x86: improve AVX512 availability check
Date: Wed, 17 Nov 2021 09:42:58 +0100 [thread overview]
Message-ID: <11371020.GgT9NJ4QQr@thomas> (raw)
In-Reply-To: <20211112214826.333853-1-dmitry.kozliuk@gmail.com>
12/11/2021 22:48, Dmitry Kozlyuk:
> The goal of this series is to enable cross-compilation
> of Windows binaries from Linux using MinGW with Meson 0.49 used in CI.
> It also aims to reduce difference between Unix and Windows build code.
>
> AVX512 was switched off for MinGW cross builds,
> but unfortunately in a way that is not usable with meson 0.49.
> Also, c_args was used instead of machine_args for -mno-avx512f.
> After patch 3/3, AVX512 support for MinGW cross builds
> is configured exactly the same way as for Unix builds.
> This required rewriting a Unix-specific script in patch 2/3.
> Patch 1/3 skips check of GNU binutils when LLVM suite is used:
> it is useful in general [1], and also simplifies patch 2/3.
>
> [1]: https://inbox.dpdk.org/dev/20211112160837.131994aa@sovereign
>
> Dmitry Kozlyuk (3):
> config/x86: skip GNU binutils bug check for LLVM
> buildtools: make AVX512 check script portable
> config/x86: fix MinGW cross build with meson 0.49
Applied, thanks.
Note 1: MAINTAINERS was updated for the new script.
Note 2: patch 3 cannot be backported without patch 2, so no Cc:stable on purpose.
prev parent reply other threads:[~2021-11-17 8:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-12 21:48 Dmitry Kozlyuk
2021-11-12 21:48 ` [PATCH 1/3] config/x86: skip GNU binutils bug check for LLVM Dmitry Kozlyuk
2021-11-15 9:17 ` Bruce Richardson
2021-11-12 21:48 ` [PATCH 2/3] buildtools: make AVX512 check script portable Dmitry Kozlyuk
2021-11-15 9:28 ` Bruce Richardson
2021-11-12 21:48 ` [PATCH 3/3] config/x86: fix MinGW cross build with meson 0.49 Dmitry Kozlyuk
2021-11-15 9:30 ` Bruce Richardson
2021-11-17 8:42 ` Thomas Monjalon [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=11371020.GgT9NJ4QQr@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).