[xen staging-4.19] xen/build: pass -fzero-init-padding-bits=all to gcc15

[patchbot@xxxxxxx]

commit 79ec6818da8b19660e2636400793f768f959eb09
Author:     Jan Beulich <jbeulich@xxxxxxxx>
AuthorDate: Mon Jul 7 11:35:48 2025 +0200
Commit:     Jan Beulich <jbeulich@xxxxxxxx>
CommitDate: Mon Jul 7 11:35:48 2025 +0200

    xen/build: pass -fzero-init-padding-bits=all to gcc15
    
    See the respective bullet point in the Caveats section of
    https://gcc.gnu.org/gcc-15/changes.html.
    
    While I'm unaware of us currently relying on the pre-gcc15 behavior,
    let's still play safe and retain what unknowingly we may have been
    relying upon.
    
    According to my observations, on x86 generated code changes
    - somewhere deep in modify_bars(), presumably from the struct map_data
      initializer in apply_map() (a new MOVQ),
    - in vpci_process_pending(), apparently again from the struct map_data
      initializer (and again a new MOVQ),
    - near the top of find_cpio_data(), presumably from the struct cpio_data
      initializer (a MOVW changing to a MOVQ).
    
    Requested-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Acked-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    master commit: 86da14178db4f40b5652e96c332d9858ca23df06
    master date: 2025-07-01 11:23:59 +0200
---
 xen/Makefile | 1 +
 1 file changed, 1 insertion(+)

diff --git a/xen/Makefile b/xen/Makefile
index a346568743..3c3110bada 100644
--- a/xen/Makefile
+++ b/xen/Makefile
@@ -393,6 +393,7 @@ endif
 CFLAGS-$(CONFIG_CC_SPLIT_SECTIONS) += -ffunction-sections -fdata-sections
 
 CFLAGS += -nostdinc -fno-builtin -fno-common
+$(call cc-option-add,CFLAGS,CC,-fzero-init-padding-bits=all)
 CFLAGS += -Werror -Wredundant-decls -Wwrite-strings -Wno-pointer-arith
 CFLAGS += -Wdeclaration-after-statement -Wuninitialized
 $(call cc-option-add,CFLAGS,CC,-Wvla)
--
generated by git-patchbot for /home/xen/git/xen.git#staging-4.19