From: Andrew Rybchenko <arybchenko@solarflare.com>
To: David Marchand <david.marchand@redhat.com>, <dev@dpdk.org>
Cc: <thomas@monjalon.net>, <stable@dpdk.org>,
Neil Horman <nhorman@tuxdriver.com>
Subject: Re: [dpdk-dev] [PATCH 2/2] buildtools: fix build with coverage enabled
Date: Mon, 25 Nov 2019 11:28:49 +0300 [thread overview]
Message-ID: <52d83c50-ec1e-c7d2-f757-bfa8482bf968@solarflare.com> (raw)
In-Reply-To: <20191125081007.12396-2-david.marchand@redhat.com>
On 11/25/19 11:10 AM, David Marchand wrote:
> A compiler can reuse a variable name and prefix it when instrumenting
> with coverage.
>
> Example:
> $ make defconfig T=x86_64-native-linux-gcc O=master
> $ make EXTRA_CFLAGS='--coverage' O=master
> [...]
> CC rte_flow.o
> rte_flow_dynf_metadata_offs is not flagged as experimental but is listed
> in version map
> Please add __rte_experimental to the definition of
> rte_flow_dynf_metadata_offs
>
> $ objdump -t master/build/lib/librte_ethdev/rte_flow.o |grep _offs$
> 0000000000000000 l F .text.startup 000000000000000a
> _GLOBAL__sub_I_65535_0_rte_flow_dynf_metadata_offs
> 0000000000000620 g O .data 0000000000000004
> rte_flow_dynf_metadata_offs
>
> Protect against this by adding a space character in the pattern.
>
> Fixes: a4bcd61de82d ("buildtools: add script to check experimental API exports")
> Cc: stable@dpdk.org
>
> Reported-by: Andrew Rybchenko <arybchenko@solarflare.com>
> Signed-off-by: David Marchand <david.marchand@redhat.com>
David,
thanks a lot, it solves build problem.
It does not solve experimental symbol inconsistency problem in
markup and map file, but it is a separate less critical
problem.
Tested-by: Andrew Rybchenko <arybchenko@solarflare.com>
next prev parent reply other threads:[~2019-11-25 8:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 8:10 [dpdk-dev] [PATCH 1/2] buildtools: fix experimental symbols listing David Marchand
2019-11-25 8:10 ` [dpdk-dev] [PATCH 2/2] buildtools: fix build with coverage enabled David Marchand
2019-11-25 8:28 ` Andrew Rybchenko [this message]
2019-11-25 10:57 ` David Marchand
2019-11-25 8:21 ` [dpdk-dev] [PATCH 1/2] buildtools: fix experimental symbols listing Andrew Rybchenko
2019-11-25 13:26 ` Neil Horman
2019-11-26 8:10 ` David Marchand
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=52d83c50-ec1e-c7d2-f757-bfa8482bf968@solarflare.com \
--to=arybchenko@solarflare.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=nhorman@tuxdriver.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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).