From: kernel test robot <lkp@intel.com>
To: Gao Xiang <hsiangkao@linux.alibaba.com>
Cc: oe-kbuild-all@lists.linux.dev, Xiang Gao <xiang@kernel.org>
Subject: [xiang:lz4-macros 1/1] lib/lz4/lz4defs.h:96:22: error: 'LZ4_MAX_DISTANCE' undeclared; did you mean 'MAX_DISTANCE'?
Date: Tue, 14 Jan 2025 20:15:45 +0800 [thread overview]
Message-ID: <202501142028.mAPCyAD2-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/xiang/linux.git lz4-macros
head: cc151de616805bc027b30cfc99853989274e2a2d
commit: cc151de616805bc027b30cfc99853989274e2a2d [1/1] include/linux/lz4.h: add some missing macros
config: arc-randconfig-002-20250114 (https://download.01.org/0day-ci/archive/20250114/202501142028.mAPCyAD2-lkp@intel.com/config)
compiler: arc-elf-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250114/202501142028.mAPCyAD2-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202501142028.mAPCyAD2-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from lib/lz4/lz4_compress.c:36:
lib/lz4/lz4_compress.c: In function 'LZ4_compress_generic':
>> lib/lz4/lz4defs.h:96:22: error: 'LZ4_MAX_DISTANCE' undeclared (first use in this function); did you mean 'MAX_DISTANCE'?
96 | #define MAX_DISTANCE LZ4_MAX_DISTANCE
| ^~~~~~~~~~~~~~~~
lib/lz4/lz4_compress.c:287:52: note: in expansion of macro 'MAX_DISTANCE'
287 | : (match + MAX_DISTANCE < ip))
| ^~~~~~~~~~~~
lib/lz4/lz4defs.h:96:22: note: each undeclared identifier is reported only once for each function it appears in
96 | #define MAX_DISTANCE LZ4_MAX_DISTANCE
| ^~~~~~~~~~~~~~~~
lib/lz4/lz4_compress.c:287:52: note: in expansion of macro 'MAX_DISTANCE'
287 | : (match + MAX_DISTANCE < ip))
| ^~~~~~~~~~~~
lib/lz4/lz4_compress.c: In function 'LZ4_compress_destSize_generic':
>> lib/lz4/lz4defs.h:96:22: error: 'LZ4_MAX_DISTANCE' undeclared (first use in this function); did you mean 'MAX_DISTANCE'?
96 | #define MAX_DISTANCE LZ4_MAX_DISTANCE
| ^~~~~~~~~~~~~~~~
lib/lz4/lz4_compress.c:597:44: note: in expansion of macro 'MAX_DISTANCE'
597 | : (match + MAX_DISTANCE < ip))
| ^~~~~~~~~~~~
--
In file included from lib/lz4/lz4hc_compress.c:37:
lib/lz4/lz4hc_compress.c: In function 'LZ4HC_Insert':
>> lib/lz4/lz4defs.h:96:22: error: 'LZ4_MAX_DISTANCE' undeclared (first use in this function); did you mean 'MAX_DISTANCE'?
96 | #define MAX_DISTANCE LZ4_MAX_DISTANCE
| ^~~~~~~~~~~~~~~~
lib/lz4/lz4hc_compress.c:86:29: note: in expansion of macro 'MAX_DISTANCE'
86 | if (delta > MAX_DISTANCE)
| ^~~~~~~~~~~~
lib/lz4/lz4defs.h:96:22: note: each undeclared identifier is reported only once for each function it appears in
96 | #define MAX_DISTANCE LZ4_MAX_DISTANCE
| ^~~~~~~~~~~~~~~~
lib/lz4/lz4hc_compress.c:86:29: note: in expansion of macro 'MAX_DISTANCE'
86 | if (delta > MAX_DISTANCE)
| ^~~~~~~~~~~~
vim +96 lib/lz4/lz4defs.h
95
> 96 #define MAX_DISTANCE LZ4_MAX_DISTANCE
97 #define STEPSIZE sizeof(size_t)
98
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-01-14 12:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202501142028.mAPCyAD2-lkp@intel.com \
--to=lkp@intel.com \
--cc=hsiangkao@linux.alibaba.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=xiang@kernel.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.