* next-20250909: selftests/arm64/gcs/basic-gcs.c:390:30: error: use of undeclared identifier 'HWCAP_GCS'
@ 2025-09-11 19:18 Naresh Kamboju
2025-09-11 21:01 ` Mark Brown
2025-09-12 6:30 ` Thomas Weißschuh
0 siblings, 2 replies; 10+ messages in thread
From: Naresh Kamboju @ 2025-09-11 19:18 UTC (permalink / raw)
To: open list, Linux ARM, open list:KERNEL SELFTEST FRAMEWORK,
lkft-triage, Linux Regressions
Cc: Mark Brown, Catalin Marinas, Thomas Weißschuh, Will Deacon,
Arnd Bergmann, Dan Carpenter, Anders Roxell, Ben Copeland,
Shuah Khan
The following build warnings / errors noticed on arm64 defconfig
with clang-20 and gcc-13 toolchains on the Linux next-20250909
till next-20250911 tag while building selftests/arm64.
Regression Analysis:
- New regression? Yes
- Reproducibility? yes
First seen on next-20250909
Good: next-20250908
Bad: next-20250909 till next-20250911
Test regression: next-20250909:
selftests/arm64/gcs/basic-gcs.c:390:30: error: use of undeclared
identifier 'HWCAP_GCS'
Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
## Build log
selftests/arm64/gcs/basic-gcs.c:390:30: error: use of undeclared
identifier 'HWCAP_GCS'
390 | if (!(getauxval(AT_HWCAP) & HWCAP_GCS))
| ^
1 error generated.
The suspected commit pointing to,
kselftest/arm64/gcs: Use nolibc's getauxval()
a985fe638344492727528e52416211dda1c391d5
## Source
* Kernel version: 6.17.0-rc5
* Git tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next.git
* Git describe: 6.17.0-rc5-next-20250911
* Git commit: 8f21d9da46702c4d6951ba60ca8a05f42870fe8f
* Architectures: arm64
* Toolchains: gcc-13 and clang-20
* Kconfigs: defconfig
## Build
* Build log: https://qa-reports.linaro.org/api/testruns/29827060/log_file/
* Build details:
https://regressions.linaro.org/lkft/linux-next-master/next-20250909/log-parser-build-clang/clang-compiler-basic-gcs_c-error-use-of-undeclared-identifier-hwcap_gcs/
* Build plan: https://tuxapi.tuxsuite.com/v1/groups/linaro/projects/lkft/builds/32RzudgbCUiqGUoFtquJ9IEIDXZ
* Build link: https://storage.tuxsuite.com/public/linaro/lkft/builds/32RzudgbCUiqGUoFtquJ9IEIDXZ/
* Kernel config:
https://storage.tuxsuite.com/public/linaro/lkft/builds/32RzudgbCUiqGUoFtquJ9IEIDXZ/config
## Steps to reproduce
$ tuxmake --runtime podman --target-arch arm64 \
--toolchain clang-nightly \
--kconfig https://storage.tuxsuite.com/public/linaro/lkft/builds/32RzudgbCUiqGUoFtquJ9IEIDXZ/config
\
LLVM=1 LLVM_IAS=1 debugkernel dtbs dtbs-legacy headers kernel kselftest modules
--
Linaro LKFT
^ permalink raw reply [flat|nested] 10+ messages in thread* Re: next-20250909: selftests/arm64/gcs/basic-gcs.c:390:30: error: use of undeclared identifier 'HWCAP_GCS'
2025-09-11 19:18 next-20250909: selftests/arm64/gcs/basic-gcs.c:390:30: error: use of undeclared identifier 'HWCAP_GCS' Naresh Kamboju
@ 2025-09-11 21:01 ` Mark Brown
2025-09-12 6:30 ` Thomas Weißschuh
1 sibling, 0 replies; 10+ messages in thread
From: Mark Brown @ 2025-09-11 21:01 UTC (permalink / raw)
To: Naresh Kamboju
Cc: open list, Linux ARM, open list:KERNEL SELFTEST FRAMEWORK,
lkft-triage, Linux Regressions, Catalin Marinas,
Thomas Weißschuh, Will Deacon, Arnd Bergmann, Dan Carpenter,
Anders Roxell, Ben Copeland, Shuah Khan
[-- Attachment #1: Type: text/plain, Size: 786 bytes --]
On Fri, Sep 12, 2025 at 12:48:47AM +0530, Naresh Kamboju wrote:
> The following build warnings / errors noticed on arm64 defconfig
> with clang-20 and gcc-13 toolchains on the Linux next-20250909
> till next-20250911 tag while building selftests/arm64.
>
> Regression Analysis:
> - New regression? Yes
> - Reproducibility? yes
>
> First seen on next-20250909
> Good: next-20250908
> Bad: next-20250909 till next-20250911
>
> Test regression: next-20250909:
> selftests/arm64/gcs/basic-gcs.c:390:30: error: use of undeclared
> identifier 'HWCAP_GCS'
This will be due to Thomas Weißschuh's nolibc changes which went in
during that time period and did change the program to use nolibc's
getauxval, presumably that's broken with this clang version or
something?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: next-20250909: selftests/arm64/gcs/basic-gcs.c:390:30: error: use of undeclared identifier 'HWCAP_GCS'
2025-09-11 19:18 next-20250909: selftests/arm64/gcs/basic-gcs.c:390:30: error: use of undeclared identifier 'HWCAP_GCS' Naresh Kamboju
2025-09-11 21:01 ` Mark Brown
@ 2025-09-12 6:30 ` Thomas Weißschuh
2025-09-12 10:23 ` Naresh Kamboju
2025-09-12 10:49 ` Mark Brown
1 sibling, 2 replies; 10+ messages in thread
From: Thomas Weißschuh @ 2025-09-12 6:30 UTC (permalink / raw)
To: Naresh Kamboju
Cc: open list, Linux ARM, open list:KERNEL SELFTEST FRAMEWORK,
lkft-triage, Linux Regressions, Mark Brown, Catalin Marinas,
Will Deacon, Arnd Bergmann, Dan Carpenter, Anders Roxell,
Ben Copeland, Shuah Khan
Hi Naresh,
On 2025-09-12 00:48:47+0530, Naresh Kamboju wrote:
> The following build warnings / errors noticed on arm64 defconfig
> with clang-20 and gcc-13 toolchains on the Linux next-20250909
> till next-20250911 tag while building selftests/arm64.
>
> Regression Analysis:
> - New regression? Yes
> - Reproducibility? yes
>
> First seen on next-20250909
> Good: next-20250908
> Bad: next-20250909 till next-20250911
>
> Test regression: next-20250909:
> selftests/arm64/gcs/basic-gcs.c:390:30: error: use of undeclared
> identifier 'HWCAP_GCS'
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
> ## Build log
> selftests/arm64/gcs/basic-gcs.c:390:30: error: use of undeclared
> identifier 'HWCAP_GCS'
> 390 | if (!(getauxval(AT_HWCAP) & HWCAP_GCS))
> | ^
> 1 error generated.
>
> The suspected commit pointing to,
> kselftest/arm64/gcs: Use nolibc's getauxval()
> a985fe638344492727528e52416211dda1c391d5
That suspicion looks correct. I am wondering a bit how this works for
the other selftests which use this symbol.
Can you give this one a try:
diff --git a/tools/testing/selftests/arm64/gcs/gcs-util.h b/tools/testing/selftests/arm64/gcs/gcs-util.h
index c99a6b39ac14..816b497634d6 100644
--- a/tools/testing/selftests/arm64/gcs/gcs-util.h
+++ b/tools/testing/selftests/arm64/gcs/gcs-util.h
@@ -26,6 +26,10 @@ struct user_gcs {
};
#endif
+#ifndef HWCAP_GCS
+#define HWCAP_GCS (1UL << 32)
+#endif
+
/* Shadow Stack/Guarded Control Stack interface */
#define PR_GET_SHADOW_STACK_STATUS 74
#define PR_SET_SHADOW_STACK_STATUS 75
^ permalink raw reply related [flat|nested] 10+ messages in thread* Re: next-20250909: selftests/arm64/gcs/basic-gcs.c:390:30: error: use of undeclared identifier 'HWCAP_GCS'
2025-09-12 6:30 ` Thomas Weißschuh
@ 2025-09-12 10:23 ` Naresh Kamboju
2025-09-12 10:49 ` Mark Brown
1 sibling, 0 replies; 10+ messages in thread
From: Naresh Kamboju @ 2025-09-12 10:23 UTC (permalink / raw)
To: Thomas Weißschuh
Cc: open list, Linux ARM, open list:KERNEL SELFTEST FRAMEWORK,
lkft-triage, Linux Regressions, Mark Brown, Catalin Marinas,
Will Deacon, Arnd Bergmann, Dan Carpenter, Anders Roxell,
Ben Copeland, Shuah Khan
Hi Thomas,
On Fri, 12 Sept 2025 at 12:00, Thomas Weißschuh <linux@weissschuh.net> wrote:
>
> Hi Naresh,
>
> On 2025-09-12 00:48:47+0530, Naresh Kamboju wrote:
> > The following build warnings / errors noticed on arm64 defconfig
> > with clang-20 and gcc-13 toolchains on the Linux next-20250909
> > till next-20250911 tag while building selftests/arm64.
> >
> > Regression Analysis:
> > - New regression? Yes
> > - Reproducibility? yes
> >
> > First seen on next-20250909
> > Good: next-20250908
> > Bad: next-20250909 till next-20250911
> >
> > Test regression: next-20250909:
> > selftests/arm64/gcs/basic-gcs.c:390:30: error: use of undeclared
> > identifier 'HWCAP_GCS'
> >
> > Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> >
> > ## Build log
> > selftests/arm64/gcs/basic-gcs.c:390:30: error: use of undeclared
> > identifier 'HWCAP_GCS'
> > 390 | if (!(getauxval(AT_HWCAP) & HWCAP_GCS))
> > | ^
> > 1 error generated.
> >
> > The suspected commit pointing to,
> > kselftest/arm64/gcs: Use nolibc's getauxval()
> > a985fe638344492727528e52416211dda1c391d5
>
> That suspicion looks correct. I am wondering a bit how this works for
> the other selftests which use this symbol.
>
> Can you give this one a try:
>
I have applied this patch and tested and reported build regressions
got fixed.
Tested-by: Linux Kernel Functional Testing <lkft@linaro.org>
> diff --git a/tools/testing/selftests/arm64/gcs/gcs-util.h b/tools/testing/selftests/arm64/gcs/gcs-util.h
> index c99a6b39ac14..816b497634d6 100644
> --- a/tools/testing/selftests/arm64/gcs/gcs-util.h
> +++ b/tools/testing/selftests/arm64/gcs/gcs-util.h
> @@ -26,6 +26,10 @@ struct user_gcs {
> };
> #endif
>
> +#ifndef HWCAP_GCS
> +#define HWCAP_GCS (1UL << 32)
> +#endif
> +
> /* Shadow Stack/Guarded Control Stack interface */
> #define PR_GET_SHADOW_STACK_STATUS 74
> #define PR_SET_SHADOW_STACK_STATUS 75
--
Linaro LKFT
^ permalink raw reply [flat|nested] 10+ messages in thread* Re: next-20250909: selftests/arm64/gcs/basic-gcs.c:390:30: error: use of undeclared identifier 'HWCAP_GCS'
2025-09-12 6:30 ` Thomas Weißschuh
2025-09-12 10:23 ` Naresh Kamboju
@ 2025-09-12 10:49 ` Mark Brown
2025-09-12 10:57 ` Thomas Weißschuh
1 sibling, 1 reply; 10+ messages in thread
From: Mark Brown @ 2025-09-12 10:49 UTC (permalink / raw)
To: Thomas Weißschuh
Cc: Naresh Kamboju, open list, Linux ARM,
open list:KERNEL SELFTEST FRAMEWORK, lkft-triage,
Linux Regressions, Catalin Marinas, Will Deacon, Arnd Bergmann,
Dan Carpenter, Anders Roxell, Ben Copeland, Shuah Khan
[-- Attachment #1: Type: text/plain, Size: 753 bytes --]
On Fri, Sep 12, 2025 at 08:30:08AM +0200, Thomas Weißschuh wrote:
> On 2025-09-12 00:48:47+0530, Naresh Kamboju wrote:
> index c99a6b39ac14..816b497634d6 100644
> --- a/tools/testing/selftests/arm64/gcs/gcs-util.h
> +++ b/tools/testing/selftests/arm64/gcs/gcs-util.h
> @@ -26,6 +26,10 @@ struct user_gcs {
> };
> #endif
>
> +#ifndef HWCAP_GCS
> +#define HWCAP_GCS (1UL << 32)
> +#endif
> +
We're doing that for glibc using tests because there's some unfortunate
interaction between including the relevant kernel header and glibc's
headers (I forget the details) which means that including the kernel
header directly conflicts with something glibc is doing. For nolibc I
would expect us to using the kernel's hwcap definitions?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 10+ messages in thread* Re: next-20250909: selftests/arm64/gcs/basic-gcs.c:390:30: error: use of undeclared identifier 'HWCAP_GCS'
2025-09-12 10:49 ` Mark Brown
@ 2025-09-12 10:57 ` Thomas Weißschuh
2025-09-12 11:07 ` Thomas Weißschuh
0 siblings, 1 reply; 10+ messages in thread
From: Thomas Weißschuh @ 2025-09-12 10:57 UTC (permalink / raw)
To: Mark Brown
Cc: Naresh Kamboju, open list, Linux ARM,
open list:KERNEL SELFTEST FRAMEWORK, lkft-triage,
Linux Regressions, Catalin Marinas, Will Deacon, Arnd Bergmann,
Dan Carpenter, Anders Roxell, Ben Copeland, Shuah Khan
Sep 12, 2025 12:49:58 Mark Brown <broonie@kernel.org>:
> On Fri, Sep 12, 2025 at 08:30:08AM +0200, Thomas Weißschuh wrote:
>> On 2025-09-12 00:48:47+0530, Naresh Kamboju wrote:
>
>> index c99a6b39ac14..816b497634d6 100644
>> --- a/tools/testing/selftests/arm64/gcs/gcs-util.h
>> +++ b/tools/testing/selftests/arm64/gcs/gcs-util.h
>> @@ -26,6 +26,10 @@ struct user_gcs {
>> };
>> #endif
>>
>> +#ifndef HWCAP_GCS
>> +#define HWCAP_GCS (1UL << 32)
>> +#endif
>> +
>
> We're doing that for glibc using tests because there's some unfortunate
> interaction between including the relevant kernel header and glibc's
> headers (I forget the details) which means that including the kernel
> header directly conflicts with something glibc is doing. For nolibc I
> would expect us to using the kernel's hwcap definitions?
nolibc doesn't even have its own asm/hwcap.h (or any asm/ header for that matter).
So a kernel header has to be used,
maybe an old one is pulled from somewhere?
(I won't have access to a development machine today anymore)
Thomas
^ permalink raw reply [flat|nested] 10+ messages in thread* Re: next-20250909: selftests/arm64/gcs/basic-gcs.c:390:30: error: use of undeclared identifier 'HWCAP_GCS'
2025-09-12 10:57 ` Thomas Weißschuh
@ 2025-09-12 11:07 ` Thomas Weißschuh
2025-09-12 11:14 ` Mark Brown
0 siblings, 1 reply; 10+ messages in thread
From: Thomas Weißschuh @ 2025-09-12 11:07 UTC (permalink / raw)
To: Mark Brown
Cc: Naresh Kamboju, open list, Linux ARM,
open list:KERNEL SELFTEST FRAMEWORK, lkft-triage,
Linux Regressions, Catalin Marinas, Will Deacon, Arnd Bergmann,
Dan Carpenter, Anders Roxell, Ben Copeland, Shuah Khan
Sep 12, 2025 12:57:15 Thomas Weißschuh <linux@weissschuh.net>:
> Sep 12, 2025 12:49:58 Mark Brown <broonie@kernel.org>:
>
>> On Fri, Sep 12, 2025 at 08:30:08AM +0200, Thomas Weißschuh wrote:
>>> On 2025-09-12 00:48:47+0530, Naresh Kamboju wrote:
>>
>>> index c99a6b39ac14..816b497634d6 100644
>>> --- a/tools/testing/selftests/arm64/gcs/gcs-util.h
>>> +++ b/tools/testing/selftests/arm64/gcs/gcs-util.h
>>> @@ -26,6 +26,10 @@ struct user_gcs {
>>> };
>>> #endif
>>>
>>> +#ifndef HWCAP_GCS
>>> +#define HWCAP_GCS (1UL << 32)
>>> +#endif
>>> +
>>
>> We're doing that for glibc using tests because there's some unfortunate
>> interaction between including the relevant kernel header and glibc's
>> headers (I forget the details) which means that including the kernel
>> header directly conflicts with something glibc is doing. For nolibc I
>> would expect us to using the kernel's hwcap definitions?
>
> nolibc doesn't even have its own asm/hwcap.h (or any asm/ header for that matter).
> So a kernel header has to be used,
> maybe an old one is pulled from somewhere?
The Makefile does *not* use -nostdinc, so the nolibc program probably finds the toolchain's glibc asm/hwcap.h.
There also doesn't seem to be a static arm64 hwcap header in tools/include in the first place.
I am still wondering how this works for the other tests.
Thomas
^ permalink raw reply [flat|nested] 10+ messages in thread* Re: next-20250909: selftests/arm64/gcs/basic-gcs.c:390:30: error: use of undeclared identifier 'HWCAP_GCS'
2025-09-12 11:07 ` Thomas Weißschuh
@ 2025-09-12 11:14 ` Mark Brown
2025-09-15 9:23 ` Thomas Weißschuh
0 siblings, 1 reply; 10+ messages in thread
From: Mark Brown @ 2025-09-12 11:14 UTC (permalink / raw)
To: Thomas Weißschuh
Cc: Naresh Kamboju, open list, Linux ARM,
open list:KERNEL SELFTEST FRAMEWORK, lkft-triage,
Linux Regressions, Catalin Marinas, Will Deacon, Arnd Bergmann,
Dan Carpenter, Anders Roxell, Ben Copeland, Shuah Khan
[-- Attachment #1: Type: text/plain, Size: 453 bytes --]
On Fri, Sep 12, 2025 at 01:07:58PM +0200, Thomas Weißschuh wrote:
> The Makefile does *not* use -nostdinc, so the nolibc program probably finds the toolchain's glibc asm/hwcap.h.
> There also doesn't seem to be a static arm64 hwcap header in tools/include in the first place.
> I am still wondering how this works for the other tests.
make headers_install puts a copy in usr/include, probably we just need
to include that in the include path.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: next-20250909: selftests/arm64/gcs/basic-gcs.c:390:30: error: use of undeclared identifier 'HWCAP_GCS'
2025-09-12 11:14 ` Mark Brown
@ 2025-09-15 9:23 ` Thomas Weißschuh
2025-09-15 19:14 ` Naresh Kamboju
0 siblings, 1 reply; 10+ messages in thread
From: Thomas Weißschuh @ 2025-09-15 9:23 UTC (permalink / raw)
To: Mark Brown, Naresh Kamboju
Cc: open list, Linux ARM, open list:KERNEL SELFTEST FRAMEWORK,
lkft-triage, Linux Regressions, Catalin Marinas, Will Deacon,
Arnd Bergmann, Dan Carpenter, Anders Roxell, Ben Copeland,
Shuah Khan
On 2025-09-12 12:14:00+0100, Mark Brown wrote:
> On Fri, Sep 12, 2025 at 01:07:58PM +0200, Thomas Weißschuh wrote:
>
> > The Makefile does *not* use -nostdinc, so the nolibc program probably finds the toolchain's glibc asm/hwcap.h.
> > There also doesn't seem to be a static arm64 hwcap header in tools/include in the first place.
> > I am still wondering how this works for the other tests.
>
> make headers_install puts a copy in usr/include, probably we just need
> to include that in the include path.
Naresh, could you test the patch below?
The other custom $(CC) rules in the gcs directory are also not
respecting $(CFLAGS), but I'll leave these for now.
diff --git a/tools/testing/selftests/arm64/gcs/Makefile b/tools/testing/selftests/arm64/gcs/Makefile
index d2f3497a9..1fbbf0ca1 100644
--- a/tools/testing/selftests/arm64/gcs/Makefile
+++ b/tools/testing/selftests/arm64/gcs/Makefile
@@ -14,11 +14,11 @@ LDLIBS+=-lpthread
include ../../lib.mk
$(OUTPUT)/basic-gcs: basic-gcs.c
- $(CC) -g -fno-asynchronous-unwind-tables -fno-ident -s -Os -nostdlib \
- -static -include ../../../../include/nolibc/nolibc.h \
+ $(CC) $(CFLAGS) -fno-asynchronous-unwind-tables -fno-ident -s -nostdlib -nostdinc \
+ -static -I../../../../include/nolibc -include ../../../../include/nolibc/nolibc.h \
-I../../../../../usr/include \
-std=gnu99 -I../.. -g \
- -ffreestanding -Wall $^ -o $@ -lgcc
+ -ffreestanding $^ -o $@ -lgcc
$(OUTPUT)/gcs-stress-thread: gcs-stress-thread.S
$(CC) -nostdlib $^ -o $@
^ permalink raw reply related [flat|nested] 10+ messages in thread* Re: next-20250909: selftests/arm64/gcs/basic-gcs.c:390:30: error: use of undeclared identifier 'HWCAP_GCS'
2025-09-15 9:23 ` Thomas Weißschuh
@ 2025-09-15 19:14 ` Naresh Kamboju
0 siblings, 0 replies; 10+ messages in thread
From: Naresh Kamboju @ 2025-09-15 19:14 UTC (permalink / raw)
To: Thomas Weißschuh
Cc: Mark Brown, open list, Linux ARM,
open list:KERNEL SELFTEST FRAMEWORK, lkft-triage,
Linux Regressions, Catalin Marinas, Will Deacon, Arnd Bergmann,
Dan Carpenter, Anders Roxell, Ben Copeland, Shuah Khan
On Mon, 15 Sept 2025 at 14:53, Thomas Weißschuh <linux@weissschuh.net> wrote:
>
> On 2025-09-12 12:14:00+0100, Mark Brown wrote:
> > On Fri, Sep 12, 2025 at 01:07:58PM +0200, Thomas Weißschuh wrote:
> >
> > > The Makefile does *not* use -nostdinc, so the nolibc program probably finds the toolchain's glibc asm/hwcap.h.
> > > There also doesn't seem to be a static arm64 hwcap header in tools/include in the first place.
> > > I am still wondering how this works for the other tests.
> >
> > make headers_install puts a copy in usr/include, probably we just need
> > to include that in the include path.
>
> Naresh, could you test the patch below?
> The other custom $(CC) rules in the gcs directory are also not
> respecting $(CFLAGS), but I'll leave these for now.
I have applied this patch on top of Linux next-20250912 tag and
tested and reported build regressions got fixed.
Tested-by: Linux Kernel Functional Testing <lkft@linaro.org>
> diff --git a/tools/testing/selftests/arm64/gcs/Makefile b/tools/testing/selftests/arm64/gcs/Makefile
> index d2f3497a9..1fbbf0ca1 100644
> --- a/tools/testing/selftests/arm64/gcs/Makefile
> +++ b/tools/testing/selftests/arm64/gcs/Makefile
> @@ -14,11 +14,11 @@ LDLIBS+=-lpthread
> include ../../lib.mk
>
> $(OUTPUT)/basic-gcs: basic-gcs.c
> - $(CC) -g -fno-asynchronous-unwind-tables -fno-ident -s -Os -nostdlib \
> - -static -include ../../../../include/nolibc/nolibc.h \
> + $(CC) $(CFLAGS) -fno-asynchronous-unwind-tables -fno-ident -s -nostdlib -nostdinc \
> + -static -I../../../../include/nolibc -include ../../../../include/nolibc/nolibc.h \
> -I../../../../../usr/include \
> -std=gnu99 -I../.. -g \
> - -ffreestanding -Wall $^ -o $@ -lgcc
> + -ffreestanding $^ -o $@ -lgcc
>
> $(OUTPUT)/gcs-stress-thread: gcs-stress-thread.S
> $(CC) -nostdlib $^ -o $@
>
- Naresh
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2025-09-15 19:14 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-09-11 19:18 next-20250909: selftests/arm64/gcs/basic-gcs.c:390:30: error: use of undeclared identifier 'HWCAP_GCS' Naresh Kamboju
2025-09-11 21:01 ` Mark Brown
2025-09-12 6:30 ` Thomas Weißschuh
2025-09-12 10:23 ` Naresh Kamboju
2025-09-12 10:49 ` Mark Brown
2025-09-12 10:57 ` Thomas Weißschuh
2025-09-12 11:07 ` Thomas Weißschuh
2025-09-12 11:14 ` Mark Brown
2025-09-15 9:23 ` Thomas Weißschuh
2025-09-15 19:14 ` Naresh Kamboju
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox