All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev <dev@dpdk.org>, dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] build: explicitly enable sse4 for meson builds
Date: Fri, 3 Jan 2020 15:52:23 +0100	[thread overview]
Message-ID: <CAJFAV8wY8fTWLiuJVRkhp9sLJqxdwtEELTvXyH6DcCmHWnQLPw@mail.gmail.com> (raw)
In-Reply-To: <20200103135521.GA570@bricha3-MOBL.ger.corp.intel.com>

On Fri, Jan 3, 2020 at 2:55 PM Bruce Richardson
<bruce.richardson@intel.com> wrote:
>
> +stable
>
> This patch is probably worthwhile taking into 19.11 and 18.11 branches to
> reduce chances of failures on CI of stable trees.

+1

>
> On Mon, Dec 23, 2019 at 10:38:40AM +0000, Bruce Richardson wrote:
> > If the compiler does not recognise the specific CPU when building with the
> > default "native" machine type, sse4.2 instructions can be missing, causing
> > a build error. Rather than advising the user to change the machine type,
> > we can just turn on SSE4.2 directly. This can prevent issues with running
> > automated tests with older compilers/distros on newer hardware.
> >
> Cc: stable@dpdk.org
> > Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>

Acked-by: David Marchand <david.marchand@redhat.com>

Applied, thanks.


--
David Marchand


      reply	other threads:[~2020-01-03 14:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-17 14:08 [dpdk-dev] [PATCH] build: explicitly enable SSE4 for x86 meson builds Bruce Richardson
2019-12-23 10:38 ` [dpdk-dev] [PATCH v2] build: explicitly enable sse4 for " Bruce Richardson
2020-01-03 13:55   ` Bruce Richardson
2020-01-03 14:52     ` David Marchand [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=CAJFAV8wY8fTWLiuJVRkhp9sLJqxdwtEELTvXyH6DcCmHWnQLPw@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=stable@dpdk.org \
    /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.