From: Ruifeng Wang <ruifeng.wang@arm.com>
Cc: dev@dpdk.org, honnappa.nagarahalli@arm.com, nd@arm.com,
Ruifeng Wang <ruifeng.wang@arm.com>
Subject: [dpdk-dev] [PATCH v2 0/2] gcc build fix
Date: Fri, 27 Nov 2020 18:15:12 +0800 [thread overview]
Message-ID: <20201127101514.47329-1-ruifeng.wang@arm.com> (raw)
In-Reply-To: <20201127080903.26817-1-ruifeng.wang@arm.com>
This series fixed issues found when building project
with Gcc '-O0' option.
Ruifeng Wang (2):
eal/arm: fix gcc build for optimization level 0
net/igc: fix gcc build for optimization level 0
drivers/net/igc/base/meson.build | 3 ++-
lib/librte_eal/arm/include/rte_atomic_64.h | 2 +-
2 files changed, 3 insertions(+), 2 deletions(-)
--
2.20.1
next prev parent reply other threads:[~2020-11-27 10:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-27 8:09 [dpdk-dev] [PATCH " Ruifeng Wang
2020-11-27 8:09 ` [dpdk-dev] [PATCH 1/2] eal/arm: fix gcc build for optimization level 0 Ruifeng Wang
2020-11-27 8:39 ` David Marchand
2020-11-27 8:51 ` Jerin Jacob
2020-11-27 9:25 ` David Marchand
2020-11-27 9:33 ` Jerin Jacob
2020-11-27 9:45 ` David Marchand
2020-11-27 10:05 ` Ruifeng Wang
2020-11-27 10:28 ` Jerin Jacob
2020-11-27 9:39 ` Andrew Rybchenko
2020-11-27 9:36 ` Ruifeng Wang
2020-11-27 8:09 ` [dpdk-dev] [PATCH 2/2] net/igc: " Ruifeng Wang
2020-11-27 8:53 ` Jerin Jacob
2020-11-27 9:02 ` David Marchand
2020-11-27 12:13 ` David Marchand
2020-11-27 14:50 ` Wang, Haiyue
2020-11-27 10:15 ` Ruifeng Wang [this message]
2020-11-27 10:15 ` [dpdk-dev] [PATCH v2 1/2] eal/arm: " Ruifeng Wang
2020-11-27 13:03 ` Ruifeng Wang
2020-11-27 10:15 ` [dpdk-dev] [PATCH v2 2/2] net/igc: " Ruifeng Wang
2020-11-27 13:35 ` [dpdk-dev] [PATCH v2 0/2] gcc build fix Thomas Monjalon
2020-11-27 14:08 ` Ruifeng Wang
2020-11-27 16:03 ` [dpdk-dev] [PATCH " Thomas Monjalon
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=20201127101514.47329-1-ruifeng.wang@arm.com \
--to=ruifeng.wang@arm.com \
--cc=dev@dpdk.org \
--cc=honnappa.nagarahalli@arm.com \
--cc=nd@arm.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).