Changes in Makefile

ff5ccdb8d5bd242f1064c6f7996603e47e28d095 - Merge tag 'x86-cpu-2026-06-14' of gitolite.kernel.org:pub/scm/linux/kernel/git/tip/tip

Mon, 15 Jun 2026 11:55:17 +0200

Merge tag 'x86-cpu-2026-06-14' of gitolite.kernel.org:pub/scm/linux/kernel/git/tip/tipPull x86 cpuid updates from Ingo Molnar: - CPUID API updates (Ahmed S. Darwish): - Introduce a centralized CPUID parser - Introduce a centralized CPUID data model - Introduce - Rename cpuid_leaf()/cpuid_subleaf() APIs - treewide: Explicitly include the x86 CPUID headers - Update to x86-cpuid-db v3.1 (Maciej Wieczor-Retman) - Continued removal of pre-i586 support and related simplifications (Ingo Molnar) - Add Intel CPU model number for rugged Panther Lake (Tony Luck) - Misc fixes, updates and cleanups by Arnd Bergmann, Chao Gao, Lukas Bulwahn, Sohil Mehta, Maciej Wieczor-Retman.* tag 'x86-cpu-2026-06-14' of gitolite.kernel.org:pub/scm/linux/kernel/git/tip/tip: (25 commits) x86/cpu: Make CONFIG_X86_CX8 unconditional x86/cpu: Remove unused !CONFIG_X86_TSC code x86/cpuid: Update bitfields to x86-cpuid-db v3.1 tools/x86/kcpuid: Update bitfields to x86-cpuid-db v3.1 x86/cpu: Make CONFIG_X86_TSC unconditional MAINTAINERS: Drop obsolete FPU EMULATOR section x86/cpu: Fix a F00F bug warning and clean up surrounding code x86/cpu: Add Intel CPU model number for rugged Panther Lake x86/cpuid: Introduce a centralized CPUID parser x86/cpu: Introduce a centralized CPUID data model x86/cpuid: Introduce x86/cpuid: Rename cpuid_leaf()/cpuid_subleaf() APIs x86/cpu: Do not include the CPUID API header in asm/processor.h Documentation: core-api/cpu_hotplug: Remove stale cpu0_hotplug docs x86/cpu, cpufreq: Remove AMD ELAN support x86/fpu: Remove the math-emu/ FPU emulation library x86/fpu: Remove the 'no387' boot option x86/fpu: Remove MATH_EMULATION and related glue code treewide: Explicitly include the x86 CPUID headers x86/cpu: Remove the CONFIG_X86_INVD_BUG quirk ... List of files: /linux/arch/x86/Makefile

73f399414a84d715bb1794182aaea852b11d0962 - Merge tag 'kbuild-7.2-1' of git://git.kernel.org/pub/scm/linux/kernel/git/kbuild/linux

Mon, 15 Jun 2026 01:31:15 +0200

Merge tag 'kbuild-7.2-1' of git://git.kernel.org/pub/scm/linux/kernel/git/kbuild/linuxPull Kbuild / Kconfig updates from Nathan Chancellor: "Kbuild: - Remove broken module linking exclusion for BTF - Add documentation around how offset header files work - Include unstripped vDSO libraries in pacman packages - Bump minimum version of LLVM for building the kernel to 17.0.1 and clean up unnecessary workarounds - Use a context manager in run-clang-tools - Add dist macro value if present to release tag for RPM packages - Detect and report truncated buf_printf() output in modpost - Add __llvm_covfun and __llvm_covmap to section whitelist in modpost - Support Clang's distributed ThinLTO mode - Remove architecture specific configurations for AutoFDO and Propeller to ease individual architecture maintenance Kconfig: - Add kconfig-sym-check target to look for dangling Kconfig symbol references and invalid tristate literal values - Harden against potential NULL pointer dereference - Fix typo in Kconfig test comment"* tag 'kbuild-7.2-1' of git://git.kernel.org/pub/scm/linux/kernel/git/kbuild/linux: (31 commits) kconfig: tests: fix typo in comment kconfig: Remove the architecture specific config for Propeller kconfig: Remove the architecture specific config for AutoFDO modpost: Add __llvm_covfun and __llvm_covmap to section_white_list kconfig: add kconfig-sym-check static checker kbuild: Remove unnecessary 'T' modifier in cmd_ar_builtin_fixup kbuild: distributed build support for Clang ThinLTO kbuild: move vmlinux.a build rule to scripts/Makefile.vmlinux_a scripts: modpost: detect and report truncated buf_printf() output kbuild: rpm-pkg: append %{?dist} macro to Release tag run-clang-tools: run multiprocessing.Pool as context manager compiler-clang.h: Drop explicit version number from "all" diagnostic macro compiler-clang.h: Remove __cleanup -Wunused-variable workaround kbuild: Remove check for broken scoping with clang < 17 in CC_HAS_ASM_GOTO_OUTPUT x86/entry/vdso32: Remove conditional omission of '.cfi_offset eflags' x86/module: Revert "Deal with GOT based stack cookie load on Clang < 17" x86/build: Drop unnecessary '-ffreestanding' addition to KBUILD_CFLAGS scripts/Makefile.warn: Drop -Wformat handling for clang < 16 riscv: Drop tautological condition from TOOLCHAIN_NEEDS_OLD_ISA_SPEC riscv: Remove tautological condition from selection of ARCH_SUPPORTS_CFI ... List of files: /linux/arch/x86/Makefile

7b3281fcb43c5fce8d4d2b0996d3ac719cb5068b - x86/build: Drop unnecessary '-ffreestanding' addition to KBUILD_CFLAGS

Mon, 18 May 2026 01:05:14 +0200

x86/build: Drop unnecessary '-ffreestanding' addition to KBUILD_CFLAGSNow that the minimum supported version of LLVM for building the kernelhas been raised to 17.0.1, the addition of '-ffreestanding' toKBUILD_CFLAGS for 32-bit x86 is unnecessary, as the linked LLVM bug isresolved in all supported LLVM versions. 16cb16e0d285 ("x86/build: Remove -ffreestanding on i386 with GCC")intended to make the addition of '-ffreestanding' clang only but due toa bug in the adjusted check from d70da12453ac ("hardening: Enable i386 FORTIFY_SOURCE on Clang 16+")it has been applied for all versions of GCC and clang < 16.0.0. Thereare no known problems with removing this for GCC but if one surfaces, itcan be restored under a CONFIG_CC_IS_GCC block.Link: https://patch.msgid.link/20260517-bump-minimum-supported-llvm-version-to-17-v2-11-b3b8cda46bdd@kernel.orgSigned-off-by: Nathan Chancellor List of files: /linux/arch/x86/Makefile

4a44b17406cb5a93f90af3df9392b3a45eb336fb - rust: kasan/kbuild: fix rustc-option when cross-compiling

Thu, 07 May 2026 13:14:42 +0200

rust: kasan/kbuild: fix rustc-option when cross-compilingThe Makefile version of rustc-option currently checks whether the optionexists for the host target instead of the target actually being compiledfor. It was done this way in commit 46e24a545cdb ("rust: kasan/kbuild:fix missing flags on first build") to avoid a circular dependency ontarget.json. However, because of this, rustc-option currently does notfunction when cross-compiling from x86_64 to aarch64 ifCONFIG_SHADOW_CALL_STACK is enabled. This is because KBUILD_RUSTFLAGScontains -Zfixed-x18 under this configuration. Since that flag does notexist on the host target, rustc-option runs into a compilation failureevery time, leading to all flags being rejected as unsupported.To fix this, update rustc-option to pass a --target parameter so thatthe host target is not used. For targets using target.json, use abuilt-in target that is as close as possible to the target created withtarget.json to avoid the circular dependency on target.json.One scenario where this causes a boot failure:* Cross-compiled from x86_64 to aarch64.* With CONFIG_SHADOW_CALL_STACK=y* With CONFIG_KASAN_SW_TAGS=y* With CONFIG_KASAN_INLINE=nThen the resulting kernel image will fail to boot when it first callsinto Rust code with a crash along the lines of "Unable to handle kernelpaging request at virtual address 0ffffffc08541796". This is because thecall threshold is not specified, so rustc will inline kasan operations,but the kasan shadow offset is not specified, which leads to the inlinedkasan instructions being incorrect.Note that the -Zsanitizer=kernel-hwaddress parameter itself does notlead to a rustc-option failure despite being aarch64-specific becauseRUSTFLAGS_KASAN has not yet been added to KBUILD_RUSTFLAGS whenrustc-option is evaluated by the kasan Makefile.Cc: stable@vger.kernel.orgFixes: 46e24a545cdb ("rust: kasan/kbuild: fix missing flags on first build")Signed-off-by: Alice Ryhl Link: https://patch.msgid.link/20260507-rustc-option-cross-v2-1-2f650a49c2b5@google.com[ Edited slightly: - Reset variable to avoid using the environment. - Use a simply expanded variable flavor for simplicity. - Export variable so that behavior in sub-`make`s is consistent. This matches other variables. - Miguel ]Signed-off-by: Miguel Ojeda List of files: /linux/arch/x86/Makefile

ab05214025ee2af262591cd48df17883648bdb1a - x86/fpu: Remove MATH_EMULATION and related glue code

Thu, 15 May 2025 10:28:27 +0200

x86/fpu: Remove MATH_EMULATION and related glue codeNow that support for 486 CPUs is gone upstream, removethe x86 mathemu code integration.Signed-off-by: Ingo Molnar Reviewed-by: Arnd Bergmann Acked-by: Dave Hansen Cc: Linus Torvalds Link: https://lore.kernel.org/r/20250425084216.3913608-9-mingo@kernel.org List of files: /linux/arch/x86/Makefile

ec4c28276c140a9338700041112f64f8d7ccc3e9 - kbuild: Consolidate C dialect options

Mon, 23 Feb 2026 20:10:28 +0100

kbuild: Consolidate C dialect optionsIntroduce CC_FLAGS_DIALECT to make it easier to update the variousplaces in the tree that rely on the GNU C standard and Microsoftextensions flags atomically. All remaining uses of '-std=gnu11' and'-fms-extensions' are in the tools directory (which has its own buildsystem) and other standalone Makefiles. This will allow the kernel touse a narrower option to enable the Microsoft anonymous tagged structureextension in a simpler manner. Place the CC_FLAGS_DIALECT block afterthe configuration include (so that a future change can move theselection of the flag to Kconfig) but before thearch/$(SRCARCH)/Makefile include (so that CC_FLAGS_DIALECT is availablefor use in those Makefiles).Signed-off-by: Nathan Chancellor Reviewed-by: Nicolas Schier Acked-by: Ard Biesheuvel Acked-by: Helge Deller # pariscLink: https://patch.msgid.link/20260223-fms-anonymous-structs-v1-1-8ee406d3c36c@kernel.orgSigned-off-by: Nicolas Schier List of files: /linux/arch/x86/Makefile

b3683f3ba079940f91f4a26004250559f170eda9 - x86/entry/vdso: Update the object paths for "make vdso_install"

Fri, 16 Jan 2026 21:40:54 +0100

x86/entry/vdso: Update the object paths for "make vdso_install"The location of the vdso binary files in the object tree has changed;update "make vdso_install" to match.Closes: https://lore.kernel.org/16ea64d1-2a9b-46f9-9fcc-42958f599eb6@leemhuis.infoFixes: 693c819fedcd ("x86/entry/vdso: Refactor the vdso build")Reported-by: Thorsten Leemhuis Signed-off-by: H. Peter Anvin (Intel) Signed-off-by: Dave Hansen Link: https://patch.msgid.link/20260116204057.386268-2-hpa@zytor.com List of files: /linux/arch/x86/Makefile

a76108d05ee13cddb72b620752a80b2c3e87aee1 - x86/entry/vdso: Move vdso2c to arch/x86/tools

Tue, 16 Dec 2025 22:25:56 +0100

x86/entry/vdso: Move vdso2c to arch/x86/toolsIt is generally better to build tools in arch/x86/tools to keep hostcflags proliferation down, and to reduce makefile sequencing issues.Move the vdso build tool vdso2c into arch/x86/tools in preparation forrefactoring the vdso makefiles.Signed-off-by: H. Peter Anvin (Intel) Signed-off-by: Dave Hansen Link: https://patch.msgid.link/20251216212606.1325678-3-hpa@zytor.com List of files: /linux/arch/x86/Makefile

b04b2e7a61830cabd00c6f95308a8e2f5d82fa52 - Merge tag 'vfs-6.19-rc1.misc' of git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs

Mon, 01 Dec 2025 17:44:26 +0100

Merge tag 'vfs-6.19-rc1.misc' of git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfsPull misc vfs updates from Christian Brauner: "Features: - Cheaper MAY_EXEC handling for path lookup. This elides MAY_WRITE permission checks during path lookup and adds the IOP_FASTPERM_MAY_EXEC flag so filesystems like btrfs can avoid expensive permission work. - Hide dentry_cache behind runtime const machinery. - Add German Maglione as virtiofs co-maintainer. Cleanups: - Tidy up and inline step_into() and walk_component() for improved code generation. - Re-enable IOCB_NOWAIT writes to files. This refactors file timestamp update logic, fixing a layering bypass in btrfs when updating timestamps on device files and improving FMODE_NOCMTIME handling in VFS now that nfsd started using it. - Path lookup optimizations extracting slowpaths into dedicated routines and adding branch prediction hints for mntput_no_expire(), fd_install(), lookup_slow(), and various other hot paths. - Enable clang's -fms-extensions flag, requiring a JFS rename to avoid conflicts. - Remove spurious exports in fs/file_attr.c. - Stop duplicating union pipe_index declaration. This depends on the shared kbuild branch that brings in -fms-extensions support which is merged into this branch. - Use MD5 library instead of crypto_shash in ecryptfs. - Use largest_zero_folio() in iomap_dio_zero(). - Replace simple_strtol/strtoul with kstrtoint/kstrtouint in init and initrd code. - Various typo fixes. Fixes: - Fix emergency sync for btrfs. Btrfs requires an explicit sync_fs() call with wait == 1 to commit super blocks. The emergency sync path never passed this, leaving btrfs data uncommitted during emergency sync. - Use local kmap in watch_queue's post_one_notification(). - Add hint prints in sb_set_blocksize() for LBS dependency on THP"* tag 'vfs-6.19-rc1.misc' of git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs: (35 commits) MAINTAINERS: add German Maglione as virtiofs co-maintainer fs: inline step_into() and walk_component() fs: tidy up step_into() & friends before inlining orangefs: use inode_update_timestamps directly btrfs: fix the comment on btrfs_update_time btrfs: use vfs_utimes to update file timestamps fs: export vfs_utimes fs: lift the FMODE_NOCMTIME check into file_update_time_flags fs: refactor file timestamp update logic include/linux/fs.h: trivial fix: regualr -> regular fs/splice.c: trivial fix: pipes -> pipe's fs: mark lookup_slow() as noinline fs: add predicts based on nd->depth fs: move mntput_no_expire() slowpath into a dedicated routine fs: remove spurious exports in fs/file_attr.c watch_queue: Use local kmap in post_one_notification() fs: touch up predicts in path lookup fs: move fd_install() slowpath into a dedicated routine and provide commentary fs: hide dentry_cache behind runtime const machinery fs: touch predicts in do_dentry_open() ... List of files: /linux/arch/x86/Makefile

789521b4717fd6bd85164ba5c131f621a79c9736 - rust: kbuild: support `-Cjump-tables=n` for Rust 1.93.0

Sat, 01 Nov 2025 10:40:11 +0100

rust: kbuild: support `-Cjump-tables=n` for Rust 1.93.0Rust 1.93.0 (expected 2026-01-22) is stabilizing `-Zno-jump-tables`[1][2] as `-Cjump-tables=n` [3].Without this change, one would eventually see: RUSTC L rust/core.o error: unknown unstable option: `no-jump-tables`Thus support the upcoming version.Link: https://github.com/rust-lang/rust/issues/116592 [1]Link: https://github.com/rust-lang/rust/pull/105812 [2]Link: https://github.com/rust-lang/rust/pull/145974 [3]Reviewed-by: Alice Ryhl Reviewed-by: Trevor Gross Acked-by: Nicolas Schier Link: https://patch.msgid.link/20251101094011.1024534-1-ojeda@kernel.orgSigned-off-by: Miguel Ojeda List of files: /linux/arch/x86/Makefile

5ff8ad3909524ad55297a434f87c238224825bf4 - kbuild: Add '-fms-extensions' to areas with dedicated CFLAGS

Fri, 31 Oct 2025 02:26:28 +0100

kbuild: Add '-fms-extensions' to areas with dedicated CFLAGSThis is a follow up to commit c4781dc3d1cf ("Kbuild: enable-fms-extensions") but in a separate change due to being substantiallydifferent from the initial submission.There are many places within the kernel that use their own CFLAGSinstead of the main KBUILD_CFLAGS, meaning code written with the mainkernel's use of '-fms-extensions' in mind that may be tangentiallyincluded in these areas will result in "error: declaration does notdeclare anything" messages from the compiler.Add '-fms-extensions' to all these areas to ensure consistency, alongwith -Wno-microsoft-anon-tag to silence clang's warning about use of theextension that the kernel cares about using. parisc does not build withclang so it does not need this warning flag. LoongArch does not need iteither because -W flags from KBUILD_FLAGS are pulled into cflags-vdso.Reported-by: Christian Brauner Closes: https://lore.kernel.org/20251030-meerjungfrau-getrocknet-7b46eacc215d@brauner/Reviewed-by: Christian Brauner Acked-by: Ard Biesheuvel Signed-off-by: Nathan Chancellor List of files: /linux/arch/x86/Makefile

0d6e9ec80cebf9b378a1d3a01144e576d731c397 - x86/build: Disable SSE4a

Mon, 27 Oct 2025 12:40:59 +0100

x86/build: Disable SSE4aLeyvi Rose reported that his X86_NATIVE_CPU=y build is failing because ourinstruction decoder doesn't support SSE4a and the AMDGPU code seems to begenerating those with his compiler of choice (CLANG+LTO).Now, our normal build flags disable SSE MMX SSE2 3DNOW AVX, but thenCC_FLAGS_FPU re-enable SSE SSE2.Since nothing mentions SSE3 or SSE4, I'm assuming that -msse (or its negative)control all SSE variants -- but why then explicitly enumerate SSE2 ?Anyway, until the instruction decoder gets fixed, explicitly disallow SSE4a(an AMD specific SSE4 extension).Fixes: ea1dcca1de12 ("x86/kbuild/64: Add the CONFIG_X86_NATIVE_CPU option to locally optimize the kernel with '-march=native'")Signed-off-by: Peter Zijlstra (Intel) Signed-off-by: Borislav Petkov (AMD) Acked-by: Borislav Petkov (AMD) Acked-by: Arisu Tachibana Acked-by: Christian König Acked-by: Harry Wentland Cc: List of files: /linux/arch/x86/Makefile

22bdd6e68bbe270a916233ec5f34a13ae5e80ed9 - Merge tag 'x86_apic_for_v6.18_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip

Tue, 30 Sep 2025 22:40:35 +0200

Merge tag 'x86_apic_for_v6.18_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tipPull x86 SEV and apic updates from Borislav Petkov: - Add functionality to provide runtime firmware updates for the non-x86 parts of an AMD platform like the security processor (ASP) firmware, modules etc, for example. The intent being that these updates are interim, live fixups before a proper BIOS update can be attempted - Add guest support for AMD's Secure AVIC feature which gives encrypted guests the needed protection against a malicious hypervisor generating unexpected interrupts and injecting them into such guest, thus interfering with its operation in an unexpected and negative manner. The advantage of this scheme is that the guest determines which interrupts and when to accept them vs leaving that to the benevolence (or not) of the hypervisor - Strictly separate the startup code from the rest of the kernel where former is executed from the initial 1:1 mapping of memory. The problem was that the toolchain-generated version of the code was being executed from a different mapping of memory than what was "assumed" during code generation, needing an ever-growing pile of fixups for absolute memory references which are invalid in the early, 1:1 memory mapping during boot. The major advantage of this is that there's no need to check the 1:1 mapping portion of the code for absolute relocations anymore and get rid of the RIP_REL_REF() macro sprinkling all over the place. For more info, see Ard's very detailed writeup on this [1] - The usual cleanups and fixesLink: https://lore.kernel.org/r/CAMj1kXEzKEuePEiHB%2BHxvfQbFz0sTiHdn4B%2B%2BzVBJ2mhkPkQ4Q@mail.gmail.com [1]* tag 'x86_apic_for_v6.18_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: (49 commits) x86/boot: Drop erroneous __init annotation from early_set_pages_state() crypto: ccp - Add AMD Seamless Firmware Servicing (SFS) driver crypto: ccp - Add new HV-Fixed page allocation/free API x86/sev: Add new dump_rmp parameter to snp_leak_pages() API x86/startup/sev: Document the CPUID flow in the boot #VC handler objtool: Ignore __pi___cfi_ prefixed symbols x86/sev: Zap snp_abort() x86/apic/savic: Do not use snp_abort() x86/boot: Get rid of the .head.text section x86/boot: Move startup code out of __head section efistub/x86: Remap inittext read-execute when needed x86/boot: Create a confined code area for startup code x86/kbuild: Incorporate boot/startup/ via Kbuild makefile x86/boot: Revert "Reject absolute references in .head.text" x86/boot: Check startup code for absence of absolute relocations objtool: Add action to check for absence of absolute relocations x86/sev: Export startup routines for later use x86/sev: Move __sev_[get|put]_ghcb() into separate noinstr object x86/sev: Provide PIC aliases for SEV related data objects x86/boot: Provide PIC aliases for 5-level paging related constants ... List of files: /linux/arch/x86/Makefile

749627c3980e4421b709857e979e8aa16a4c7147 - x86/kbuild: Incorporate boot/startup/ via Kbuild makefile

Thu, 28 Aug 2025 12:22:21 +0200

x86/kbuild: Incorporate boot/startup/ via Kbuild makefileUsing core-y is not the correct way to get kbuild to descend intoarch/x86/boot/startup. For instance, building an individual object doesnot work as expected when the pattern rule is local to the Makefile $ make arch/x86/boot/startup/map_kernel.pi.o GEN Makefile CALL /home/ardb/linux/scripts/checksyscalls.sh DESCEND objtool INSTALL libsubcmd_headers make[3]: *** No rule to make target 'arch/x86/boot/startup/map_kernel.pi.o'. Stop. make[2]: *** [/home/ardb/linux/scripts/Makefile.build:461: arch/x86] Error 2 make[1]: *** [/home/ardb/linux/Makefile:2011: .] Error 2 make: *** [/home/ardb/linux/Makefile:248: __sub-make] Error 2So use obj-y from arch.x86/Kbuild instead, which makes things work asexpected.Signed-off-by: Ard Biesheuvel Signed-off-by: Borislav Petkov (AMD) Link: https://lore.kernel.org/20250828102202.1849035-42-ardb+git@google.com List of files: /linux/arch/x86/Makefile

337927d9895a800a63ffe852616ab05f5d304971 - x86/build: Remove cc-option from -mskip-rax-setup

Fri, 15 Aug 2025 03:31:41 +0200

x86/build: Remove cc-option from -mskip-rax-setupThis has been supported in GCC since 5.1 and clang since 14.0. Now that x86requires LLVM 15 or newer since 7861640aac52 ("x86/build: Raise the minimum LLVM version to 15.0.0"),this flag can be unconditionally added, saving a compiler invocation.Signed-off-by: Nathan Chancellor Signed-off-by: Borislav Petkov (AMD) Link: https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=fbe575b652f5bdcc459f447a0e6f0e059996d4efLink: https://github.com/llvm/llvm-project/commit/a9fba2be35db674971382e38b99a31403444d9bfLink: https://lore.kernel.org/20250814-x86-min-ver-cleanups-v1-5-ff7f19457523@kernel.org List of files: /linux/arch/x86/Makefile

0a42d732c136d3466cd19fafa7317d3004430318 - x86/build: Remove cc-option from -mno-fp-ret-in-387

Fri, 15 Aug 2025 03:31:40 +0200

x86/build: Remove cc-option from -mno-fp-ret-in-387This has been supported in GCC for forever and clang gained support for it asan alias of '-mno-x87' in LLVM 14. Now that x86 requires LLVM 15 or newersince 7861640aac52 ("x86/build: Raise the minimum LLVM version to 15.0.0"),this flag can be unconditionally added, saving a compiler invocation.Signed-off-by: Nathan Chancellor Signed-off-by: Borislav Petkov (AMD) Link: https://github.com/llvm/llvm-project/commit/a9fba2be35db674971382e38b99a31403444d9bfLink: https://lore.kernel.org/20250814-x86-min-ver-cleanups-v1-4-ff7f19457523@kernel.org List of files: /linux/arch/x86/Makefile

487fe3a936b0b84ef09fa324b4c01d059886f951 - x86/build: Clean up stack alignment flags in CC_FLAGS_FPU

Fri, 15 Aug 2025 03:31:39 +0200

x86/build: Clean up stack alignment flags in CC_FLAGS_FPUThe minimum supported version of GCC to build the x86 kernel was bumpedto GCC 8.1 in a3e8fe814ad1 ("x86/build: Raise the minimum GCC version to 8.1").Prior to GCC 7.1, '-mpreferred-stack-boundary=3' was not allowed with'-msse', so areas of the kernel that needed floating point had adifferent alignment. Now that GCC > 7.1 is mandatory, there is no needto have a different value of '-mpreferred-stack-boundary' from the restof the kernel, so remove this handling from CC_FLAGS_FPU.Signed-off-by: Nathan Chancellor Signed-off-by: Borislav Petkov (AMD) Link: https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=34fac449e121be97dd073c5428cc855367b2872cLink: https://lore.kernel.org/20250814-x86-min-ver-cleanups-v1-3-ff7f19457523@kernel.org List of files: /linux/arch/x86/Makefile

d87208128a3330c0eab18301ab39bdb419647730 - x86/build: Remove cc-option from stack alignment flags

Fri, 15 Aug 2025 03:31:38 +0200

x86/build: Remove cc-option from stack alignment flags'-mpreferred-stack-boundary' (the GCC option) and '-mstack-alignment'(the clang option) have been supported in their respective compilers forsome time, so it is unnecessary to check for support for them viacc-option. '-mpreferred-stack-boundary=3' had a restriction on'-mno-sse' until GCC 7.1 but that is irrelevant for most of the kernel,which includes '-mno-sse'.Move to simple Kconfig checks to avoid querying the compiler for theflags that it supports.Signed-off-by: Nathan Chancellor Signed-off-by: Borislav Petkov (AMD) Link: https://lore.kernel.org/20250814-x86-min-ver-cleanups-v1-2-ff7f19457523@kernel.org List of files: /linux/arch/x86/Makefile

5d6d30eca4dd1c9e8515a8d4b13106205d5c0ec4 - x86/build: Remove cc-option for GCC retpoline flags

Fri, 15 Aug 2025 03:31:37 +0200

x86/build: Remove cc-option for GCC retpoline flagsThe minimum supported version of GCC to build the x86 kernel was bumpedto GCC 8.1 in a3e8fe814ad1 ("x86/build: Raise the minimum GCC version to 8.1").'-mindirect-branch' and '-mindirect-branch-register' were first supported inGCC 8.1, so there is no need to call cc-option to inquire if it is supported.Signed-off-by: Nathan Chancellor Signed-off-by: Borislav Petkov (AMD) Link: https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=da99fd4a3ca06b43b08ba8d96dab84e83ac90aa7Link: https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=d543c04b795f8af4ebe5b3d5f38156ef4e5734f1Link: https://lore.kernel.org/20250814-x86-min-ver-cleanups-v1-1-ff7f19457523@kernel.org List of files: /linux/arch/x86/Makefile

914873bc7df913db988284876c16257e6ab772c6 - Merge tag 'x86-build-2025-05-25' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip

Tue, 27 May 2025 06:41:14 +0200

Merge tag 'x86-build-2025-05-25' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tipPull x86 build updates from Ingo Molnar: "Add the CONFIG_X86_NATIVE_CPU=y build option to locally optimize the kernel build with '-march=native'"* tag 'x86-build-2025-05-25' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: x86/kbuild/64: Restrict clang versions that can use '-march=native' x86/kbuild/64: Test for the availability of the -mtune=native compiler flag x86/kbuild/64: Add the CONFIG_X86_NATIVE_CPU option to locally optimize the kernel with '-march=native' List of files: /linux/arch/x86/Makefile