From: Thomas Monjalon <thomas@monjalon.net>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org, Harry van Haaren <harry.van.haaren@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3] build: check functionality rather than binutils version
Date: Sun, 05 Jul 2020 16:52:32 +0200 [thread overview]
Message-ID: <10700032.x8Otjhmkp9@thomas> (raw)
In-Reply-To: <20200704114801.1110659-1-bruce.richardson@intel.com>
04/07/2020 13:48, Bruce Richardson:
> Rather than checking the binutils version number, which can lead to
> unnecessary disabling of AVX512 if fixes have been backported to distro
> versions, we can instead check the output of "as" from binutils to see if
> it is correct.
>
> The check in the script uses the minimal assembly reproduction code posted
> to the public bug tracker for gcc/binutils for those issues [1]. If the
> binutils bug is present, the instruction parameters - specifically the
> displacement parameter - will be different in the disassembled output
> compared to the input. Therefore the check involves assembling a single
> instruction and disassembling it again, checking that the two match.
>
> [1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90028
>
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> Tested-by: Harry van Haaren <harry.van.haaren@intel.com>
>
> ---
> V3:
> - Use mktemp to create a temporary file rather than place object file in
> build folder. Use trap to ensure temp file deletion on exit.
>
> V2:
> - Renamed "as_ok" variable to "binutils_ok" for readability
> - Removed one test case from the script because even though two DPDK bugs
> were filed, the one binutils bug is the root cause, and a single commit
> fixes them both
> - Changed message() to warning() in the printout
Applied, thanks
prev parent reply other threads:[~2020-07-05 14:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 10:40 [dpdk-dev] [PATCH] build: check functionality rather than binutils version Bruce Richardson
2020-06-17 11:45 ` Thomas Monjalon
2020-06-17 14:32 ` Bruce Richardson
2020-06-18 11:56 ` [dpdk-dev] [PATCH v2] " Bruce Richardson
2020-06-18 12:05 ` Van Haaren, Harry
2020-07-02 21:28 ` Thomas Monjalon
2020-07-03 10:35 ` Bruce Richardson
2020-07-04 11:48 ` [dpdk-dev] [PATCH v3] " Bruce Richardson
2020-07-05 14:52 ` 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=10700032.x8Otjhmkp9@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.