From: Sunil Kumar Kori <skori@marvell.com>
To: "changqing.li@windriver.com" <changqing.li@windriver.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [EXTERNAL] [PATCH V4] Add new tracepoint function for type time_t
Date: Wed, 28 May 2025 16:14:11 +0000 [thread overview]
Message-ID: <CO6PR18MB386076246E0C20B3EC4F7230B467A@CO6PR18MB3860.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20250527120404.2027529-1-changqing.li@windriver.com>
> From: Changqing Li <changqing.li@windriver.com>
>
> To support Y2038 issue, for 32bit system, -D_TIME_BITS=64 is passed to gcc, struct
> timespec time->tv_sec is 64bit, but size_t is 32bits, so dpdk will compile failed
> with error:
> "../git/lib/ethdev/ethdev_trace.h: In function
> 'rte_eth_trace_timesync_write_time':
> ../git/lib/eal/include/rte_common.h:498:55: error: size of unnamed array is
> negative
> 498 | #define RTE_BUILD_BUG_ON(condition) ((void)sizeof(char[1 -
> 2*!!(condition)]))"
>
> Add a new tracepoint function for type time_t to fix this issue
>
> Signed-off-by: Changqing Li <changqing.li@windriver.com>
> ---
> lib/eal/common/eal_common_trace_ctf.c | 5 +++++
> lib/eal/include/rte_trace_point.h | 5 +++++
> lib/ethdev/ethdev_trace.h | 8 ++++----
> 3 files changed, 14 insertions(+), 4 deletions(-)
>
Acked-by: Sunil Kumar Kori <skori@marvell.com>
prev parent reply other threads:[~2025-05-28 16:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 3:00 [PATCH] " changqing.li
2025-04-29 3:04 ` [PATCH V2] " changqing.li
2025-04-30 1:34 ` [PATCH V3] " changqing.li
[not found] ` <20250430024403.2690306-1-robot@bytheb.org>
2025-04-30 5:21 ` |FAILURE| pw153190 " Changqing Li
2025-05-05 13:56 ` David Marchand
2025-05-07 2:21 ` Changqing Li
2025-05-08 13:53 ` [EXTERNAL] " Jerin Jacob
2025-05-28 8:06 ` Sunil Kumar Kori
2025-05-28 8:14 ` Changqing Li
2025-05-27 12:04 ` [PATCH V4] " changqing.li
2025-05-28 16:14 ` Sunil Kumar Kori [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=CO6PR18MB386076246E0C20B3EC4F7230B467A@CO6PR18MB3860.namprd18.prod.outlook.com \
--to=skori@marvell.com \
--cc=changqing.li@windriver.com \
--cc=dev@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 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).