drop volatile from global data
Subsystems (10)
cover drop volatile from global data
There's really no reason for the gd pointer to have the volatile qualifier.
In fact, I claim that it's completely unnecessary and just pessimizes code generation and forces ugly casts in lots of places. For example, see the casts in drivers/core/tag.c where elements are added to gd->dm_taglist, or a helper such as cyclic_get_list() that should not be needed.
Also, it is what ends up standing in the way of an otherwise innocent code cleanup of list.h:
https://lore.kernel.org/u-boot/20250522165656.GB2179216@bill-the-cat/
Note that riscv, x86 as well as arm64 with LTO enabled has not had this volatile qualifier, so it's unlikely there's any generic code that depends on it.
CI seems mostly happy:
https://github.com/u-boot/u-boot/pull/775/checks?check_run_id=43463083829
The one failing test seems to be an infrastructure thing unrelated to these patches ("docker: filesystem layer verification failed for digest sha256:379cc6cd06dc3fc80e31d5170204c0cfcc25cb3b3ad457ced23bed2b38ec9f36")
Rasmus Villemoes (12):
arm: drop volatile qualifier from gd pointer
powerpc: drop volatile qualifier from gd pointer
mips: drop volatile qualifier from gd pointer
microblaze: drop volatile qualifier from gd pointer
m68k: drop volatile qualifier from gd pointer
m68k: drop pointless #if 0 block
arc: drop volatile qualifier from gd pointer
arm: imx: remove unnecessary volatile qualifiers from "save gd"
variables
efi: drop volatile qualifier from "save gd" variables lib/trace: drop volatile qualifier from "save gd" variables
arm: remove volatile from set_gd prototype
riscv: remove volatile from set_gd prototype
arch/arc/include/asm/global_data.h | 2 +- arch/arm/include/asm/global_data.h | 6 +++--- arch/arm/mach-imx/hab.c | 2 +- arch/arm/mach-imx/imx9/scmi/soc.c | 4 ++-- arch/arm/mach-imx/romapi.c | 6 +++--- arch/m68k/include/asm/global_data.h | 7 +------ arch/microblaze/include/asm/global_data.h | 2 +- arch/mips/include/asm/global_data.h | 2 +- arch/powerpc/include/asm/global_data.h | 2 +- arch/riscv/include/asm/global_data.h | 2 +- lib/efi_loader/efi_boottime.c | 2 +- lib/trace.c | 4 ++-- 12 files changed, 18 insertions(+), 23 deletions(-)
Signature · 1 line
2.49.0
PATCH 1/12 arm: drop volatile qualifier from gd pointer
There's a bunch of other places where this qualifier should be dropped, e.g. in the set_gd() prototype and for various variables used for stashing the value in the mach-imx/ directory and elsewhere. But that will be done in follow-up patches.
--- arch/arm/include/asm/global_data.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
arch/arm/include/asm/global_data.h +2 -2
@@ -133,9 +133,9 @@ static inline gd_t *get_gd(void)#else #ifdef CONFIG_ARM64 -#define DECLARE_GLOBAL_DATA_PTR register volatile gd_t *gd asm ("x18") +#define DECLARE_GLOBAL_DATA_PTR register gd_t *gd asm ("x18")#else -#define DECLARE_GLOBAL_DATA_PTR register volatile gd_t *gd asm ("r9") +#define DECLARE_GLOBAL_DATA_PTR register gd_t *gd asm ("r9")#endif #endif
Signature · 1 line
2.49.0
Re: [PATCH 01/12] arm: drop volatile qualifier from gd pointer
Quoted 6 lines · Rasmus Villemoes
There's a bunch of other places where this qualifier should be dropped, e.g. in the
set_gd()prototype and for various variables used for stashing the value in the mach-imx/ directory and elsewhere. But that will be done in follow-up patches.Signed-off-by Rasmus Villemoes <[email protected]>
PATCH 2/12 powerpc: drop volatile qualifier from gd pointer
In reply to Rasmus Villemoes--- arch/powerpc/include/asm/global_data.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/powerpc/include/asm/global_data.h +1 -1
@@ -93,7 +93,7 @@ struct arch_global_data {#include <asm-generic/global_data.h> -#define DECLARE_GLOBAL_DATA_PTR register volatile gd_t *gd asm ("r2") +#define DECLARE_GLOBAL_DATA_PTR register gd_t *gd asm ("r2")#include <asm/u-boot.h>
Signature · 1 line
2.49.0
PATCH 3/12 mips: drop volatile qualifier from gd pointer
In reply to Rasmus Villemoes--- arch/mips/include/asm/global_data.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/mips/include/asm/global_data.h +1 -1
@@ -44,6 +44,6 @@ struct arch_global_data {#include <asm-generic/global_data.h> -#define DECLARE_GLOBAL_DATA_PTR register volatile gd_t *gd asm ("k0") +#define DECLARE_GLOBAL_DATA_PTR register gd_t *gd asm ("k0")#endif /* __ASM_GBL_DATA_H */
Signature · 1 line
2.49.0
PATCH 4/12 microblaze: drop volatile qualifier from gd pointer
In reply to Rasmus Villemoes--- arch/microblaze/include/asm/global_data.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/microblaze/include/asm/global_data.h +1 -1
@@ -18,7 +18,7 @@ struct arch_global_data {#include <asm-generic/global_data.h> -#define DECLARE_GLOBAL_DATA_PTR register volatile gd_t *gd asm ("r31") +#define DECLARE_GLOBAL_DATA_PTR register gd_t *gd asm ("r31")#define gd_cpuinfo () ((struct microblaze_cpuinfo *)&gd->arch.cpuinfo)
Signature · 1 line
2.49.0
PATCH 5/12 m68k: drop volatile qualifier from gd pointer
In reply to Rasmus Villemoes--- arch/m68k/include/asm/global_data.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/m68k/include/asm/global_data.h +1 -1
@@ -36,7 +36,7 @@ struct arch_global_data {extern gd_t *global_data;#define DECLARE_GLOBAL_DATA_PTR gd_t *gd = global_data#else -#define DECLARE_GLOBAL_DATA_PTR register volatile gd_t *gd asm ("d7") +#define DECLARE_GLOBAL_DATA_PTR register gd_t *gd asm ("d7")#endif #endif /* __ASM_GBL_DATA_H */
Signature · 1 line
2.49.0
PATCH 6/12 m68k: drop pointless #if 0 block
In reply to Rasmus VillemoesThe way DECLARE_GLOBAL_DATA_PTR is used, the stuff under #if 0 can never compile as you cannot have a non-constant initializer at global scope (and one would get linker errors as well because the 'gd' symbol would be defined in multiple TUs).
--- arch/m68k/include/asm/global_data.h | 5 ----- 1 file changed, 5 deletions(-)
arch/m68k/include/asm/global_data.h +0 -5
@@ -32,11 +32,6 @@ struct arch_global_data {#include <asm-generic/global_data.h> -#if 0 -extern gd_t *global_data; -#define DECLARE_GLOBAL_DATA_PTR gd_t *gd = global_data -#else #define DECLARE_GLOBAL_DATA_PTR register gd_t *gd asm ("d7") -#endif #endif /* __ASM_GBL_DATA_H */
Signature · 1 line
2.49.0
Re: [PATCH 06/12] m68k: drop pointless #if 0 block
thanks,
On Wed, 4 Jun 2025 21:56:06 +0200
Quoted 29 lines · Rasmus Villemoes
The way
DECLARE_GLOBAL_DATA_PTRis used, the stuff under #if 0 can never compile as you cannot have a non-constant initializer at global scope (and one would get linker errors as well because the 'gd' symbol would be defined in multiple TUs).Signed-off-by Rasmus Villemoes <[email protected]>--- arch/m68k/include/asm/global_data.h | 5 ----- 1 file changed, 5 deletions(-)arch/m68k/include/asm/global_data.h +0
-5@@ -32,11 +32,6 @@ struct arch_global_data {#include <asm-generic/global_data.h> -#if 0 -extern gd_t *global_data; -#define DECLARE_GLOBAL_DATA_PTR gd_t *gd = global_data -#else #define DECLARE_GLOBAL_DATA_PTR register gd_t *gd asm ("d7") -#endif #endif /* __ASM_GBL_DATA_H */ Signature · 1 line
2.49.0
PATCH 7/12 arc: drop volatile qualifier from gd pointer
In reply to Rasmus Villemoes--- arch/arc/include/asm/global_data.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/arc/include/asm/global_data.h +1 -1
@@ -20,6 +20,6 @@ struct arch_global_data {#include <asm-generic/global_data.h> -#define DECLARE_GLOBAL_DATA_PTR register volatile gd_t *gd asm ("r25") +#define DECLARE_GLOBAL_DATA_PTR register gd_t *gd asm ("r25")#endif /* __ASM_ARC_GLOBAL_DATA_H */
Signature · 1 line
2.49.0
PATCH 8/12 arm: imx: remove unnecessary volatile qualifiers from "save gd" variables
In reply to Rasmus VillemoesNow that the global gd pointer is no longer volatile-qualified, there's no reason for the temporary variables used for saving/restoring it to have that qualifier.
--- arch/arm/mach-imx/hab.c | 2 +- arch/arm/mach-imx/imx9/scmi/soc.c | 4 ++-- arch/arm/mach-imx/romapi.c | 6 +++--- 3 files changed, 6 insertions(+), 6 deletions(-)
arch/arm/mach-imx/hab.c +1 -1
@@ -74,7 +74,7 @@ static int verify_ivt_header(struct ivt_header *ivt_hdr)#define FSL_SIP_HAB_REPORT_STATUS 0x04#define FSL_SIP_HAB_FAILSAFE 0x05#define FSL_SIP_HAB_CHECK_TARGET 0x06 -static volatile gd_t *gd_save; +static gd_t *gd_save;#endif static inline void save_gd (void )
arch/arm/mach-imx/imx9/scmi/soc.c +2 -2
@@ -67,7 +67,7 @@ int mmc_get_env_dev(void)u16 boot_type;u8 boot_instance; -volatile gd_t *pgd = gd; +gd_t *pgd = gd;rom_passover_t *rdata;#if IS_ENABLED (CONFIG_XPL_BUILD )
@@ -675,7 +675,7 @@ enum imx9_soc_voltage_mode soc_target_voltage_mode(void)#if IS_ENABLED (CONFIG_SCMI_FIRMWARE )enum boot_device get_boot_device (void ) { -volatile gd_t *pgd = gd; +gd_t *pgd = gd;int ret;u16 boot_type;u8 boot_instance;
arch/arm/mach-imx/romapi.c +3 -3
@@ -9,7 +9,7 @@ DECLARE_GLOBAL_DATA_PTR;u32 rom_api_download_image (u8 *dest,u32 offset,u32 size) {u32 xor = (uintptr_t )dest ^ offset ^ size; -volatile gd_t *sgd = gd; +gd_t *sgd = gd;u32 ret; ret = g_rom_api->download_image (dest, offset, size, xor);
@@ -21,7 +21,7 @@ u32 rom_api_download_image(u8 *dest, u32 offset, u32 size)u32 rom_api_query_boot_infor (u32 info_type,u32 *info) {u32 xor = info_type ^ (uintptr_t )info; -volatile gd_t *sgd = gd; +gd_t *sgd = gd;u32 ret; ret = g_rom_api->query_boot_infor (info_type, info, xor);
@@ -34,7 +34,7 @@ extern struct rom_api *g_rom_api;enum boot_device get_boot_device (void ) { -volatile gd_t *pgd = gd; +gd_t *pgd = gd;int ret;u32 boot;u16 boot_type;
Signature · 1 line
2.49.0
Re: [PATCH 08/12] arm: imx: remove unnecessary volatile qualifiers from "save gd" variables
Quoted 5 lines · Rasmus Villemoes
Now that the global gd pointer is no longer volatile-qualified, there's no reason for the temporary variables used for saving/restoring it to have that qualifier.
Signed-off-by Rasmus Villemoes <[email protected]>
PATCH 9/12 efi: drop volatile qualifier from "save gd" variables
In reply to Rasmus VillemoesThe global gd pointer is no longer volatile-qualified, so drop that qualifier from these bookkeeping variables.
--- lib/efi_loader/efi_boottime.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
lib/efi_loader/efi_boottime.c +1 -1
@@ -58,7 +58,7 @@ static efi_handle_t current_image;* restriction so we need to manually swap its and our view of that register on * EFI callback entry/exit. */ -static volatile gd_t *efi_gd, *app_gd; +static gd_t *efi_gd, *app_gd;#endif efi_status_t efi_uninstall_protocol
Signature · 1 line
2.49.0
Re: [PATCH 09/12] efi: drop volatile qualifier from "save gd" variables
Am 4. Juni 2025 21:56:09 MESZ schrieb Rasmus Villemoes <[email protected]>:
Quoted 4 lines
The global gd pointer is no longer volatile-qualified, so drop that qualifier from these bookkeeping variables.
Signed-off-by Rasmus Villemoes <[email protected]>
Quoted 17 lines
---
lib/efi_loader/efi_boottime.c| 2 +-1 file changed, 1 insertion(+), 1 deletion(-)lib/efi_loader/efi_boottime.c +1
-1@@ -58,7 +58,7 @@ static efi_handle_t current_image;* restriction so we need to manually swap its and our view of that register on * EFI callback entry/exit. */ -static volatile gd_t *efi_gd, *app_gd; +static gd_t *efi_gd, *app_gd;#endif
efi_status_tefi_uninstall_protocol
PATCH 10/12 lib/trace: drop volatile qualifier from "save gd" variables
In reply to Rasmus VillemoesThe global gd pointer is no longer volatile-qualified, so drop that qualifier from these bookkeeping variables.
--- lib/trace.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
lib/trace.c +2 -2
@@ -66,7 +66,7 @@ static inline uintptr_t __attribute__((no_instrument_function))/** * trace_gd - the value of the gd register */ -static volatile gd_t *trace_gd; +static gd_t *trace_gd;/** * trace_save_gd() - save the value of the gd register
@@ -86,7 +86,7 @@ static void notrace trace_save_gd(void)*/ static void notrace trace_swap_gd(void) { -volatile gd_t *temp_gd = trace_gd; +gd_t *temp_gd = trace_gd; trace_gd = gd;set_gd (temp_gd);
Signature · 1 line
2.49.0
PATCH 11/12 arm: remove volatile from set_gd prototype
In reply to Rasmus VillemoesThe global gd pointer is no longer volatile-qualified. Callers of this helper function have been updated to no longer use volatile-qualifed temporary variables, so update the prototype accordingly.
--- arch/arm/include/asm/global_data.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/arm/include/asm/global_data.h +1 -1
@@ -139,7 +139,7 @@ static inline gd_t *get_gd(void)#endif #endif -static inline void set_gd (volatile gd_t *gd_ptr) +static inline void set_gd (gd_t *gd_ptr) {#ifdef CONFIG_ARM64 __asm__volatile ("ldr x18, %0\n" : :"m" (gd_ptr));
Signature · 1 line
2.49.0
PATCH 12/12 riscv: remove volatile from set_gd prototype
In reply to Rasmus VillemoesIt's slightly ironic that riscv at very first had the gd pointer volatile qualified [6020faf62c3 ("riscv: nx25: include: Add header files to support RISC-V")], removed that back in 2018 [40717eb849c ("riscv: checkpatch: Fix use of volatile")], and then in 2020 this helper was added [6b9966e1aa3 ("riscv: define function set_gd()")] which needlessly had volatile in the prototype.
--- arch/riscv/include/asm/global_data.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/riscv/include/asm/global_data.h +1 -1
@@ -68,7 +68,7 @@ static inline gd_t *get_gd(void)#endif -static inline void set_gd (volatile gd_t *gd_ptr) +static inline void set_gd (gd_t *gd_ptr) {#ifdef CONFIG_64BIT asmvolatile ("ld gp, %0\n" : :"m" (gd_ptr));
Signature · 1 line
2.49.0
Quoted 17 lines · Rasmus Villemoes
There's really no reason for the gd pointer to have the volatile qualifier.
In fact, I claim that it's completely unnecessary and just pessimizes code generation and forces ugly casts in lots of places. For example, see the casts in
drivers/core/tag.cwhere elements are added togd->dm_taglist, or a helper such ascyclic_get_list()that should not be needed.Also, it is what ends up standing in the way of an otherwise innocent code cleanup of
list.h:
https://lore.kernel.org/u-boot/20250522165656.GB2179216@bill-the-cat/Note that riscv, x86 as well as arm64 with LTO enabled has not had this volatile qualifier, so it's unlikely there's any generic code that depends on it.
Quoted 8 lines
CI seems mostly happy:
https://github.com/u-boot/u-boot/pull/775/checks?check_run_id=43463083829
The one failing test seems to be an infrastructure thing unrelated to these patches ("docker: filesystem layer verification failed for digest sha256:379cc6cd06dc3fc80e31d5170204c0cfcc25cb3b3ad457ced23bed2b38ec9f36")
Azure seems to be having some hiccups, sadly. I know from my end I can't hit "rerun failed jobs", is there an option visible to you like that? Thanks.
Signature · 1 line
Tom
Quoted 22 lines · Tom Rini
Quoted 21 lines · Rasmus Villemoes
There's really no reason for the gd pointer to have the volatile qualifier.
In fact, I claim that it's completely unnecessary and just pessimizes code generation and forces ugly casts in lots of places. For example, see the casts in
drivers/core/tag.cwhere elements are added togd->dm_taglist, or a helper such ascyclic_get_list()that should not be needed.Also, it is what ends up standing in the way of an otherwise innocent code cleanup of
list.h:
https://lore.kernel.org/u-boot/20250522165656.GB2179216@bill-the-cat/Note that riscv, x86 as well as arm64 with LTO enabled has not had this volatile qualifier, so it's unlikely there's any generic code that depends on it.
CI seems mostly happy:
https://github.com/u-boot/u-boot/pull/775/checks?check_run_id=43463083829
Quoted 7 lines
Quoted 4 lines
The one failing test seems to be an infrastructure thing unrelated to these patches ("docker: filesystem layer verification failed for digest sha256:379cc6cd06dc3fc80e31d5170204c0cfcc25cb3b3ad457ced23bed2b38ec9f36")
Azure seems to be having some hiccups, sadly. I know from my end I can't hit "rerun failed jobs", is there an option visible to you like that?
Technically yes, practically no.
On
https://dev.azure.com/u-boot/u-boot/_build/results?buildId=11303&view=results,
I see a "Rerun failed jobs" button. Clicking that, I get a popup saying
Rerun Stage
Are you sure you want to rerun failed jobs in the stage 'world_build'?
and after clicking yes, a banner with red(dish) background appears at the top of the page with text
TF400813: The user 'aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa' is not authorized to access this resource.
and after that the "Rerun" button is greyed out.
I can do a trivial change the commit log for the first patch and force-push, which triggers a new round of tests, but I don't know if it's worth it. I think the current revision is the third time I've had CI chew on it before sending the series to the list, and each time there's been at least one test failing, every time for reasons I've deemed unrelated to the patches.
Rasmus
Quoted 47 lines · Rasmus Villemoes
Quoted 22 lines · Tom Rini
Quoted 21 lines · Rasmus Villemoes
There's really no reason for the gd pointer to have the volatile qualifier.
In fact, I claim that it's completely unnecessary and just pessimizes code generation and forces ugly casts in lots of places. For example, see the casts in
drivers/core/tag.cwhere elements are added togd->dm_taglist, or a helper such ascyclic_get_list()that should not be needed.Also, it is what ends up standing in the way of an otherwise innocent code cleanup of
list.h:
https://lore.kernel.org/u-boot/20250522165656.GB2179216@bill-the-cat/Note that riscv, x86 as well as arm64 with LTO enabled has not had this volatile qualifier, so it's unlikely there's any generic code that depends on it.
CI seems mostly happy:
https://github.com/u-boot/u-boot/pull/775/checks?check_run_id=43463083829
Quoted 7 lines
Quoted 4 lines
The one failing test seems to be an infrastructure thing unrelated to these patches ("docker: filesystem layer verification failed for digest sha256:379cc6cd06dc3fc80e31d5170204c0cfcc25cb3b3ad457ced23bed2b38ec9f36")
Azure seems to be having some hiccups, sadly. I know from my end I can't hit "rerun failed jobs", is there an option visible to you like that?
Technically yes, practically no.
On
https://dev.azure.com/u-boot/u-boot/_build/results?buildId=11303&view=results,
I see a "Rerun failed jobs" button. Clicking that, I get a popup sayingRerun Stage
Are you sure you want to rerun failed jobs in the stage '
world_build'?and after clicking yes, a banner with red(dish) background appears at the top of the page with text
TF400813: The user 'aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa' is not authorized to access this resource.
Quoted 8 lines
and after that the "Rerun" button is greyed out.
I can do a trivial change the commit log for the first patch and force-push, which triggers a new round of tests, but I don't know if it's worth it. I think the current revision is the third time I've had CI chew on it before sending the series to the list, and each time there's been at least one test failing, every time for reasons I've deemed unrelated to the patches.
Azure is annoying at times, sigh. I re-ran the failed part and the build is green now. Thanks for looking.
Signature · 1 line
Tom
Quoted 22 lines · Tom Rini
Quoted 21 lines · Rasmus Villemoes
There's really no reason for the gd pointer to have the volatile qualifier.
In fact, I claim that it's completely unnecessary and just pessimizes code generation and forces ugly casts in lots of places. For example, see the casts in
drivers/core/tag.cwhere elements are added togd->dm_taglist, or a helper such ascyclic_get_list()that should not be needed.Also, it is what ends up standing in the way of an otherwise innocent code cleanup of
list.h:
https://lore.kernel.org/u-boot/20250522165656.GB2179216@bill-the-cat/Note that riscv, x86 as well as arm64 with LTO enabled has not had this volatile qualifier, so it's unlikely there's any generic code that depends on it.
CI seems mostly happy:
https://github.com/u-boot/u-boot/pull/775/checks?check_run_id=43463083829
Quoted 7 lines
Quoted 4 lines
The one failing test seems to be an infrastructure thing unrelated to these patches ("docker: filesystem layer verification failed for digest sha256:379cc6cd06dc3fc80e31d5170204c0cfcc25cb3b3ad457ced23bed2b38ec9f36")
Azure seems to be having some hiccups, sadly. I know from my end I can't hit "rerun failed jobs", is there an option visible to you like that?
Ah, this was a different Azure problem (I was looking like I was logged in and authorized, but was in fact not authorized) so I hit the retry failed jobs button now.
Signature · 1 line
Tom
Quoted 10 lines · Rasmus Villemoes
There's really no reason for the gd pointer to have the volatile qualifier.
In fact, I claim that it's completely unnecessary and just pessimizes code generation and forces ugly casts in lots of places. For example, see the casts in
drivers/core/tag.cwhere elements are added togd->dm_taglist, or a helper such ascyclic_get_list()that should not be needed.[...]
Applied to u-boot/next, thanks!
[01/12] arm: drop volatile qualifier from gd pointer
commit: 45fa0014ba56fc52765d66edda489933ce0e9871
[02/12] powerpc: drop volatile qualifier from gd pointer
commit: aa53d9bb7d7b470eaa62e53550d66546f80d2446
[03/12] mips: drop volatile qualifier from gd pointer
commit: 344c7e091c2033be4a5cb8bf73c08d8cf020b77d
[04/12] microblaze: drop volatile qualifier from gd pointer
commit: fe0fa2bb6635ce3826b38204e68b284ada3a79fe
[05/12] m68k: drop volatile qualifier from gd pointer
commit: e66d7fc089912a8f84bbbfa4a69eb5c0ebaa1e1d
[06/12] m68k: drop pointless #if 0 block
commit: a6f3d70a6bc2f99ac86f47bc5697d7e6e36ea7b8
[07/12] arc: drop volatile qualifier from gd pointer
commit: 30b97f58f20e58ea5bb1d5dce7253c58d03629d5
[08/12] arm: imx: remove unnecessary volatile qualifiers from "save gd" variables
commit: 01869368c08278d19a0b7ec744013bc88afcf09a
[09/12] efi: drop volatile qualifier from "save gd" variables
commit: 83b040983c92446c284c7b4ee5f97c60c6ab5afc
[10/12] lib/trace: drop volatile qualifier from "save gd" variables
commit: abe705be4751dfd5ae2ed0c24971cd4417f645ad
[11/12] arm: remove volatile from set_gd prototype
commit: ce55643546a59c05d6c4b181c2b490b6db7ba1f5
[12/12] riscv: remove volatile from set_gd prototype
commit: ae86cd8c59fe08c9a37d14dbd6e42190dda2a0d4Signature · 1 line
Tom