From: David Marchand <david.marchand@redhat.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dpdk-dev <dev@dpdk.org>, Thomas Monjalon <thomas@monjalon.net>,
Kevin Traynor <ktraynor@redhat.com>,
Yipeng Wang <yipeng1.wang@intel.com>,
Sameh Gobriel <sameh.gobriel@intel.com>,
Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [dpdk-dev] DPDK Release Status Meeting 14/05/2020
Date: Thu, 14 May 2020 13:49:07 +0200 [thread overview]
Message-ID: <CAJFAV8w9ZAY+44z=zW6s4DZ6Q44r2kQ2koN2WW9np_PMEC2n8Q@mail.gmail.com> (raw)
In-Reply-To: <f4a3b8e7-9aa1-cbc6-e05f-55d636031a09@intel.com>
On Thu, May 14, 2020 at 1:18 PM Ferruh Yigit <ferruh.yigit@intel.com> wrote:
>
> On 5/14/2020 12:13 PM, Ferruh Yigit wrote:
> > Minutes 14 May 2020
> > -------------------
>
> <...>
>
> > * gcc10
> > * Akhil's fix for crypto looks good, can replace temporary solution
> > * Gavin has patch for mbuf, but this stage can be late/risky for complex fix
> > * At this stage we can go with disabling warning as temporary solution
> > * Ferruh is getting a warning on hash too, will share it
>
> Hi David,
>
> Following is what I am getting [1] with compiler version:
> gcc (GCC) 10.1.1 20200511
Ah.
I just saw that my fedora (rawhide) did not have this version yet...
upgraded and I reproduce the issue.
gcc version 10.1.1 20200507 (Red Hat 10.1.1-1) (GCC)
Kevin confirmed that fc32 switched to 10.1.1 version too.
Thanks.
--
David Marchand
next prev parent reply other threads:[~2020-05-14 11:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 11:13 Ferruh Yigit
2020-05-14 11:17 ` Ferruh Yigit
2020-05-14 11:49 ` David Marchand [this message]
2020-05-15 14:31 ` Kevin Traynor
2020-05-14 13:44 ` Ferruh Yigit
2020-05-15 16:14 ` Thomas Monjalon
2020-05-21 5:47 ` Ajit Khaparde
2020-05-21 8:28 ` Iremonger, Bernard
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='CAJFAV8w9ZAY+44z=zW6s4DZ6Q44r2kQ2koN2WW9np_PMEC2n8Q@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=ktraynor@redhat.com \
--cc=sameh.gobriel@intel.com \
--cc=thomas@monjalon.net \
--cc=yipeng1.wang@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 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).