From: kernel test robot <lkp@intel.com>
To: Charlie Jenkins via B4 Relay
<devnull+thecharlesjenkins.gmail.com@kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>,
Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Sergey Matyukevich <geomatsi@gmail.com>,
Andy Chiu <andybnac@gmail.com>, Deepak Gupta <debug@rivosinc.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kselftest@vger.kernel.org,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
Charlie Jenkins <thecharlesjenkins@gmail.com>
Subject: Re: [PATCH 1/4] selftests: riscv: Add definition of BIT() macro
Date: Thu, 5 Mar 2026 17:10:34 +0100 [thread overview]
Message-ID: <202603051713.xu4BUyLe-lkp@intel.com> (raw)
In-Reply-To: <20260305-fix_selftests-v1-1-61b62d23500b@gmail.com>
Hi Charlie,
kernel test robot noticed the following build errors:
[auto build test ERROR on c107785c7e8dbabd1c18301a1c362544b5786282]
url: https://github.com/intel-lab-lkp/linux/commits/Charlie-Jenkins-via-B4-Relay/selftests-riscv-Add-definition-of-BIT-macro/20260305-164838
base: c107785c7e8dbabd1c18301a1c362544b5786282
patch link: https://lore.kernel.org/r/20260305-fix_selftests-v1-1-61b62d23500b%40gmail.com
patch subject: [PATCH 1/4] selftests: riscv: Add definition of BIT() macro
config: riscv-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20260305/202603051713.xu4BUyLe-lkp@intel.com/config)
compiler: riscv64-linux-gnu-gcc (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260305/202603051713.xu4BUyLe-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/202603051713.xu4BUyLe-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from /usr/riscv64-linux-gnu/include/stdint.h:34,
from /usr/lib/gcc-cross/riscv64-linux-gnu/14/include/stdint.h:9,
from tools/testing/selftests/../../../tools/include/linux/types.h:7,
from ./../../../../include/nolibc/std.h:19,
from ./../../../../include/nolibc/nolibc.h:95,
from <command-line>:
>> /usr/riscv64-linux-gnu/include/bits/stdint-intn.h:27:19: error: conflicting types for 'int64_t'; have '__int64_t' {aka 'long int'}
27 | typedef __int64_t int64_t;
| ^~~~~~~
In file included from ./../../../../include/nolibc/std.h:16:
./../../../../include/nolibc/stdint.h:17:29: note: previous declaration of 'int64_t' with type 'int64_t' {aka 'long long int'}
17 | typedef signed long long int64_t;
| ^~~~~~~
In file included from /usr/riscv64-linux-gnu/include/stdint.h:37:
>> /usr/riscv64-linux-gnu/include/bits/stdint-uintn.h:27:20: error: conflicting types for 'uint64_t'; have '__uint64_t' {aka 'long unsigned int'}
27 | typedef __uint64_t uint64_t;
| ^~~~~~~~
./../../../../include/nolibc/stdint.h:16:28: note: previous declaration of 'uint64_t' with type 'uint64_t' {aka 'long long unsigned int'}
16 | typedef unsigned long long uint64_t;
| ^~~~~~~~
In file included from /usr/riscv64-linux-gnu/include/stdint.h:41:
>> /usr/riscv64-linux-gnu/include/bits/stdint-least.h:28:25: error: conflicting types for 'int_least64_t'; have '__int_least64_t' {aka 'long int'}
28 | typedef __int_least64_t int_least64_t;
| ^~~~~~~~~~~~~
./../../../../include/nolibc/stdint.h:30:23: note: previous declaration of 'int_least64_t' with type 'int_least64_t' {aka 'long long int'}
30 | typedef int64_t int_least64_t;
| ^~~~~~~~~~~~~
>> /usr/riscv64-linux-gnu/include/bits/stdint-least.h:34:26: error: conflicting types for 'uint_least64_t'; have '__uint_least64_t' {aka 'long unsigned int'}
34 | typedef __uint_least64_t uint_least64_t;
| ^~~~~~~~~~~~~~
./../../../../include/nolibc/stdint.h:31:22: note: previous declaration of 'uint_least64_t' with type 'uint_least64_t' {aka 'long long unsigned int'}
31 | typedef uint64_t uint_least64_t;
| ^~~~~~~~~~~~~~
>> /usr/riscv64-linux-gnu/include/stdint.h:51:33: error: conflicting types for 'int_fast64_t'; have 'long int'
51 | typedef long int int_fast64_t;
| ^~~~~~~~~~~~
./../../../../include/nolibc/stdint.h:39:24: note: previous declaration of 'int_fast64_t' with type 'int_fast64_t' {aka 'long long int'}
39 | typedef int64_t int_fast64_t;
| ^~~~~~~~~~~~
>> /usr/riscv64-linux-gnu/include/stdint.h:64:33: error: conflicting types for 'uint_fast64_t'; have 'long unsigned int'
64 | typedef unsigned long int uint_fast64_t;
| ^~~~~~~~~~~~~
./../../../../include/nolibc/stdint.h:40:23: note: previous declaration of 'uint_fast64_t' with type 'uint_fast64_t' {aka 'long long unsigned int'}
40 | typedef uint64_t uint_fast64_t;
| ^~~~~~~~~~~~~
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: Charlie Jenkins via B4 Relay
<devnull+thecharlesjenkins.gmail.com@kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>,
Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Sergey Matyukevich <geomatsi@gmail.com>,
Andy Chiu <andybnac@gmail.com>, Deepak Gupta <debug@rivosinc.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kselftest@vger.kernel.org,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
Charlie Jenkins <thecharlesjenkins@gmail.com>
Subject: Re: [PATCH 1/4] selftests: riscv: Add definition of BIT() macro
Date: Thu, 5 Mar 2026 17:10:34 +0100 [thread overview]
Message-ID: <202603051713.xu4BUyLe-lkp@intel.com> (raw)
In-Reply-To: <20260305-fix_selftests-v1-1-61b62d23500b@gmail.com>
Hi Charlie,
kernel test robot noticed the following build errors:
[auto build test ERROR on c107785c7e8dbabd1c18301a1c362544b5786282]
url: https://github.com/intel-lab-lkp/linux/commits/Charlie-Jenkins-via-B4-Relay/selftests-riscv-Add-definition-of-BIT-macro/20260305-164838
base: c107785c7e8dbabd1c18301a1c362544b5786282
patch link: https://lore.kernel.org/r/20260305-fix_selftests-v1-1-61b62d23500b%40gmail.com
patch subject: [PATCH 1/4] selftests: riscv: Add definition of BIT() macro
config: riscv-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20260305/202603051713.xu4BUyLe-lkp@intel.com/config)
compiler: riscv64-linux-gnu-gcc (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260305/202603051713.xu4BUyLe-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/202603051713.xu4BUyLe-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from /usr/riscv64-linux-gnu/include/stdint.h:34,
from /usr/lib/gcc-cross/riscv64-linux-gnu/14/include/stdint.h:9,
from tools/testing/selftests/../../../tools/include/linux/types.h:7,
from ./../../../../include/nolibc/std.h:19,
from ./../../../../include/nolibc/nolibc.h:95,
from <command-line>:
>> /usr/riscv64-linux-gnu/include/bits/stdint-intn.h:27:19: error: conflicting types for 'int64_t'; have '__int64_t' {aka 'long int'}
27 | typedef __int64_t int64_t;
| ^~~~~~~
In file included from ./../../../../include/nolibc/std.h:16:
./../../../../include/nolibc/stdint.h:17:29: note: previous declaration of 'int64_t' with type 'int64_t' {aka 'long long int'}
17 | typedef signed long long int64_t;
| ^~~~~~~
In file included from /usr/riscv64-linux-gnu/include/stdint.h:37:
>> /usr/riscv64-linux-gnu/include/bits/stdint-uintn.h:27:20: error: conflicting types for 'uint64_t'; have '__uint64_t' {aka 'long unsigned int'}
27 | typedef __uint64_t uint64_t;
| ^~~~~~~~
./../../../../include/nolibc/stdint.h:16:28: note: previous declaration of 'uint64_t' with type 'uint64_t' {aka 'long long unsigned int'}
16 | typedef unsigned long long uint64_t;
| ^~~~~~~~
In file included from /usr/riscv64-linux-gnu/include/stdint.h:41:
>> /usr/riscv64-linux-gnu/include/bits/stdint-least.h:28:25: error: conflicting types for 'int_least64_t'; have '__int_least64_t' {aka 'long int'}
28 | typedef __int_least64_t int_least64_t;
| ^~~~~~~~~~~~~
./../../../../include/nolibc/stdint.h:30:23: note: previous declaration of 'int_least64_t' with type 'int_least64_t' {aka 'long long int'}
30 | typedef int64_t int_least64_t;
| ^~~~~~~~~~~~~
>> /usr/riscv64-linux-gnu/include/bits/stdint-least.h:34:26: error: conflicting types for 'uint_least64_t'; have '__uint_least64_t' {aka 'long unsigned int'}
34 | typedef __uint_least64_t uint_least64_t;
| ^~~~~~~~~~~~~~
./../../../../include/nolibc/stdint.h:31:22: note: previous declaration of 'uint_least64_t' with type 'uint_least64_t' {aka 'long long unsigned int'}
31 | typedef uint64_t uint_least64_t;
| ^~~~~~~~~~~~~~
>> /usr/riscv64-linux-gnu/include/stdint.h:51:33: error: conflicting types for 'int_fast64_t'; have 'long int'
51 | typedef long int int_fast64_t;
| ^~~~~~~~~~~~
./../../../../include/nolibc/stdint.h:39:24: note: previous declaration of 'int_fast64_t' with type 'int_fast64_t' {aka 'long long int'}
39 | typedef int64_t int_fast64_t;
| ^~~~~~~~~~~~
>> /usr/riscv64-linux-gnu/include/stdint.h:64:33: error: conflicting types for 'uint_fast64_t'; have 'long unsigned int'
64 | typedef unsigned long int uint_fast64_t;
| ^~~~~~~~~~~~~
./../../../../include/nolibc/stdint.h:40:23: note: previous declaration of 'uint_fast64_t' with type 'uint_fast64_t' {aka 'long long unsigned int'}
40 | typedef uint64_t uint_fast64_t;
| ^~~~~~~~~~~~~
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2026-03-05 16:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 8:11 [PATCH 0/4] selftests: riscv: Fix compilation issues for v_ptrace and cfi Charlie Jenkins
2026-03-05 8:11 ` Charlie Jenkins via B4 Relay
2026-03-05 8:11 ` Charlie Jenkins via B4 Relay
2026-03-05 8:11 ` [PATCH 1/4] selftests: riscv: Add definition of BIT() macro Charlie Jenkins
2026-03-05 8:11 ` Charlie Jenkins via B4 Relay
2026-03-05 8:11 ` Charlie Jenkins via B4 Relay
2026-03-05 16:10 ` kernel test robot [this message]
2026-03-05 16:10 ` kernel test robot
2026-03-05 8:11 ` [PATCH 2/4] selftests: riscv: Add braces around EXPECT_EQ() Charlie Jenkins
2026-03-05 8:11 ` Charlie Jenkins via B4 Relay
2026-03-05 8:11 ` Charlie Jenkins via B4 Relay
2026-03-05 8:11 ` [PATCH 3/4] riscv: ptrace: Fix BIT() compilation issues Charlie Jenkins
2026-03-05 8:11 ` Charlie Jenkins via B4 Relay
2026-03-05 8:11 ` Charlie Jenkins via B4 Relay
2026-03-05 8:11 ` [PATCH 4/4] selftests: riscv: Add license to cfi selftest Charlie Jenkins
2026-03-05 8:11 ` Charlie Jenkins via B4 Relay
2026-03-05 8:11 ` Charlie Jenkins via B4 Relay
2026-03-09 21:21 ` [PATCH 0/4] selftests: riscv: Fix compilation issues for v_ptrace and cfi Sergey Matyukevich
2026-03-09 21:21 ` Sergey Matyukevich
2026-03-10 1:45 ` Charlie Jenkins
2026-03-10 1:45 ` Charlie Jenkins
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=202603051713.xu4BUyLe-lkp@intel.com \
--to=lkp@intel.com \
--cc=andybnac@gmail.com \
--cc=debug@rivosinc.com \
--cc=devnull+thecharlesjenkins.gmail.com@kernel.org \
--cc=geomatsi@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=thecharlesjenkins@gmail.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 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.