Hello,
by this change, the config has below difference with parent after building.
--- /pkg/linux/x86_64-randconfig-003-20241025/clang-19/af0121c2d303111d363c62e40413ffb39d5dc0f1/.config 2024-10-26 03:31:02.494416152 +0800
+++ /pkg/linux/x86_64-randconfig-003-20241025/clang-19/8b8ca9c25fe69c2162e3235c7d6c341127abeed6/.config 2024-10-25 23:52:03.899366299 +0800
@@ -661,6 +661,8 @@ CONFIG_LTO_NONE=y
CONFIG_ARCH_SUPPORTS_CFI_CLANG=y
CONFIG_ARCH_USES_CFI_TRAPS=y
CONFIG_CFI_CLANG=y
+CONFIG_CFI_ICALL_NORMALIZE_INTEGERS=y
+CONFIG_HAVE_CFI_ICALL_NORMALIZE_INTEGERS_CLANG=y
# CONFIG_CFI_PERMISSIVE is not set
CONFIG_HAVE_ARCH_WITHIN_STACK_FRAMES=y
CONFIG_HAVE_CONTEXT_TRACKING_USER=y
then we noticed the boot jobs which can pass on parent, failed now.
=========================================================================================
tbox_group/testcase/rootfs/kconfig/compiler/sleep:
vm-snb/boot/yocto-x86_64-minimal-20190520.cgz/x86_64-randconfig-003-20241025/clang-19/1
af0121c2d303111d 8b8ca9c25fe69c2162e3235c7d6
---------------- ---------------------------
fail:runs %reproduction fail:runs
| | |
:6 100% 6:6 dmesg.CFI_failure_at_do_basic_setup
:6 100% 6:6 dmesg.Kernel_panic-not_syncing:Fatal_exception
:6 100% 6:6 dmesg.Oops:invalid_opcode:#[##]PREEMPT_KASAN
:6 100% 6:6 dmesg.RIP:do_basic_setup
:6 100% 6:6 dmesg.boot_failures
below report just FYI what we observed in our tests. thanks
kernel test robot noticed "CFI_failure_at_do_basic_setup" on:
commit: 8b8ca9c25fe69c2162e3235c7d6c341127abeed6 ("cfi: fix conditions for HAVE_CFI_ICALL_NORMALIZE_INTEGERS")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
[test failed on linus/master c71f8fb4dc911022748a378b16aad1cc9b43aad8]
[test failed on linux-next/master a39230ecf6b3057f5897bc4744a790070cfbe7a8]
in testcase: boot
config: x86_64-randconfig-003-20241025
compiler: clang-19
test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
(please refer to attached dmesg/kmsg for entire log/backtrace)
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 <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202410281414.c351044e-oliver.sang@intel.com
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20241028/202410281414.c351044e-oliver.sang@intel.com
[ 7.616732][ T1] CFI failure at do_basic_setup+0x5b/0x90 (target: asan.module_ctor+0x0/0x20; expected type: 0xe5c47d60)
[ 7.617229][ T1] Oops: invalid opcode: 0000 [#1] PREEMPT KASAN
[ 7.617952][ T1] CPU: 0 UID: 0 PID: 1 Comm: swapper Not tainted 6.12.0-rc2-00005-g8b8ca9c25fe6 #1 c804d49ce32901c4caca8ebfe1766898b63e48de
[ 7.619334][ T1] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
[ 7.620488][ T1] RIP: 0010:do_basic_setup+0x5b/0x90
[ 7.620842][ T1] Code: 00 fc ff df 48 89 d8 48 c1 e8 03 42 80 3c 38 00 74 08 48 89 df e8 6d 85 50 fb 4d 8b 5e f8 41 ba a0 82 3b 1a 45 03 53 fc 74 02 <0f> 0b 41 ff d3 49 81 fe 68 10 7e be 73 0f e8 8a eb 12 fb 48 83 c3
[ 7.620842][ T1] RSP: 0000:ffffc9000001fed0 EFLAGS: 00010286
[ 7.620842][ T1] RAX: 1ffffffff7cfb6de RBX: ffffffffbe7db6f0 RCX: 0000000000000000
[ 7.620842][ T1] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
[ 7.620842][ T1] RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
[ 7.620842][ T1] R10: 00000000bf7be9ac R11: ffffffffbbdc9360 R12: ffffffffbd039fc0
[ 7.620842][ T1] R13: 0000000000000000 R14: ffffffffbe7db6f8 R15: dffffc0000000000
[ 7.620842][ T1] FS: 0000000000000000(0000) GS:ffffffffbd0dc000(0000) knlGS:0000000000000000
[ 7.620842][ T1] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 7.620842][ T1] CR2: ffff88843ffff000 CR3: 000000042529e000 CR4: 00000000000406f0
[ 7.620842][ T1] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 7.620842][ T1] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[ 7.620842][ T1] Call Trace:
[ 7.620842][ T1] <TASK>
[ 7.620842][ T1] ? __die_body+0x16/0x68
[ 7.620842][ T1] ? die+0x34/0x58
[ 7.620842][ T1] ? do_trap+0x111/0x1e8
[ 7.620842][ T1] ? do_basic_setup+0x5b/0x90
[ 7.620842][ T1] ? do_error_trap+0x11a/0x190
[ 7.620842][ T1] ? do_basic_setup+0x5b/0x90
[ 7.620842][ T1] ? handle_invalid_op+0x34/0x50
[ 7.620842][ T1] ? do_basic_setup+0x5b/0x90
[ 7.620842][ T1] ? exc_invalid_op+0x32/0x48
[ 7.620842][ T1] ? asm_exc_invalid_op+0x16/0x20
[ 7.620842][ T1] ? __cfi_asan.module_ctor+0x10/0x10
[ 7.620842][ T1] ? do_basic_setup+0x5b/0x90
[ 7.620842][ T1] kernel_init_freeable+0xf0/0x190
[ 7.620842][ T1] ? __cfi_kernel_init+0x8/0x8
[ 7.620842][ T1] kernel_init+0x19/0x198
[ 7.620842][ T1] ? __cfi_kernel_init+0x8/0x8
[ 7.620842][ T1] ret_from_fork+0x5a/0x88
[ 7.620842][ T1] ? __cfi_kernel_init+0x8/0x8
[ 7.620842][ T1] ret_from_fork_asm+0x11/0x20
[ 7.620842][ T1] </TASK>
[ 7.620842][ T1] Modules linked in:
[ 7.620846][ T1] ---[ end trace 0000000000000000 ]---
[ 7.621487][ T1] RIP: 0010:do_basic_setup+0x5b/0x90
[ 7.622107][ T1] Code: 00 fc ff df 48 89 d8 48 c1 e8 03 42 80 3c 38 00 74 08 48 89 df e8 6d 85 50 fb 4d 8b 5e f8 41 ba a0 82 3b 1a 45 03 53 fc 74 02 <0f> 0b 41 ff d3 49 81 fe 68 10 7e be 73 0f e8 8a eb 12 fb 48 83 c3
[ 7.624206][ T1] RSP: 0000:ffffc9000001fed0 EFLAGS: 00010286
[ 7.624847][ T1] RAX: 1ffffffff7cfb6de RBX: ffffffffbe7db6f0 RCX: 0000000000000000
[ 7.625768][ T1] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
[ 7.626696][ T1] RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
[ 7.627602][ T1] R10: 00000000bf7be9ac R11: ffffffffbbdc9360 R12: ffffffffbd039fc0
[ 7.628513][ T1] R13: 0000000000000000 R14: ffffffffbe7db6f8 R15: dffffc0000000000
[ 7.629316][ T1] FS: 0000000000000000(0000) GS:ffffffffbd0dc000(0000) knlGS:0000000000000000
[ 7.630979][ T1] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 7.632216][ T1] CR2: ffff88843ffff000 CR3: 000000042529e000 CR4: 00000000000406f0
[ 7.633336][ T1] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 7.634842][ T1] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[ 7.636376][ T1] Kernel panic - not syncing: Fatal exception
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
On Mon, Oct 28, 2024 at 7:24 AM kernel test robot <oliver.sang@intel.com> wrote: > > Hello, > > by this change, the config has below difference with parent after building. > > --- /pkg/linux/x86_64-randconfig-003-20241025/clang-19/af0121c2d303111d363c62e40413ffb39d5dc0f1/.config 2024-10-26 03:31:02.494416152 +0800 > +++ /pkg/linux/x86_64-randconfig-003-20241025/clang-19/8b8ca9c25fe69c2162e3235c7d6c341127abeed6/.config 2024-10-25 23:52:03.899366299 +0800 > @@ -661,6 +661,8 @@ CONFIG_LTO_NONE=y > CONFIG_ARCH_SUPPORTS_CFI_CLANG=y > CONFIG_ARCH_USES_CFI_TRAPS=y > CONFIG_CFI_CLANG=y > +CONFIG_CFI_ICALL_NORMALIZE_INTEGERS=y > +CONFIG_HAVE_CFI_ICALL_NORMALIZE_INTEGERS_CLANG=y > # CONFIG_CFI_PERMISSIVE is not set > CONFIG_HAVE_ARCH_WITHIN_STACK_FRAMES=y > CONFIG_HAVE_CONTEXT_TRACKING_USER=y > > then we noticed the boot jobs which can pass on parent, failed now. > > ========================================================================================= > tbox_group/testcase/rootfs/kconfig/compiler/sleep: > vm-snb/boot/yocto-x86_64-minimal-20190520.cgz/x86_64-randconfig-003-20241025/clang-19/1 > > af0121c2d303111d 8b8ca9c25fe69c2162e3235c7d6 > ---------------- --------------------------- > fail:runs %reproduction fail:runs > | | | > :6 100% 6:6 dmesg.CFI_failure_at_do_basic_setup > :6 100% 6:6 dmesg.Kernel_panic-not_syncing:Fatal_exception > :6 100% 6:6 dmesg.Oops:invalid_opcode:#[##]PREEMPT_KASAN > :6 100% 6:6 dmesg.RIP:do_basic_setup > :6 100% 6:6 dmesg.boot_failures > > > below report just FYI what we observed in our tests. thanks > > > kernel test robot noticed "CFI_failure_at_do_basic_setup" on: > > commit: 8b8ca9c25fe69c2162e3235c7d6c341127abeed6 ("cfi: fix conditions for HAVE_CFI_ICALL_NORMALIZE_INTEGERS") > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master > > [test failed on linus/master c71f8fb4dc911022748a378b16aad1cc9b43aad8] > [test failed on linux-next/master a39230ecf6b3057f5897bc4744a790070cfbe7a8] > > in testcase: boot > > config: x86_64-randconfig-003-20241025 > compiler: clang-19 > test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G > > (please refer to attached dmesg/kmsg for entire log/backtrace) > > > > 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 <oliver.sang@intel.com> > | Closes: https://lore.kernel.org/oe-lkp/202410281414.c351044e-oliver.sang@intel.com > > > > The kernel config and materials to reproduce are available at: > https://download.01.org/0day-ci/archive/20241028/202410281414.c351044e-oliver.sang@intel.com > > > > [ 7.616732][ T1] CFI failure at do_basic_setup+0x5b/0x90 (target: asan.module_ctor+0x0/0x20; expected type: 0xe5c47d60) > [ 7.617229][ T1] Oops: invalid opcode: 0000 [#1] PREEMPT KASAN > [ 7.617952][ T1] CPU: 0 UID: 0 PID: 1 Comm: swapper Not tainted 6.12.0-rc2-00005-g8b8ca9c25fe6 #1 c804d49ce32901c4caca8ebfe1766898b63e48de > [ 7.619334][ T1] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/01/2014 > [ 7.620488][ T1] RIP: 0010:do_basic_setup+0x5b/0x90 > [ 7.620842][ T1] Code: 00 fc ff df 48 89 d8 48 c1 e8 03 42 80 3c 38 00 74 08 48 89 df e8 6d 85 50 fb 4d 8b 5e f8 41 ba a0 82 3b 1a 45 03 53 fc 74 02 <0f> 0b 41 ff d3 49 81 fe 68 10 7e be 73 0f e8 8a eb 12 fb 48 83 c3 > [ 7.620842][ T1] RSP: 0000:ffffc9000001fed0 EFLAGS: 00010286 > [ 7.620842][ T1] RAX: 1ffffffff7cfb6de RBX: ffffffffbe7db6f0 RCX: 0000000000000000 > [ 7.620842][ T1] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 > [ 7.620842][ T1] RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 > [ 7.620842][ T1] R10: 00000000bf7be9ac R11: ffffffffbbdc9360 R12: ffffffffbd039fc0 > [ 7.620842][ T1] R13: 0000000000000000 R14: ffffffffbe7db6f8 R15: dffffc0000000000 > [ 7.620842][ T1] FS: 0000000000000000(0000) GS:ffffffffbd0dc000(0000) knlGS:0000000000000000 > [ 7.620842][ T1] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 > [ 7.620842][ T1] CR2: ffff88843ffff000 CR3: 000000042529e000 CR4: 00000000000406f0 > [ 7.620842][ T1] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 > [ 7.620842][ T1] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 > [ 7.620842][ T1] Call Trace: > [ 7.620842][ T1] <TASK> > [ 7.620842][ T1] ? __die_body+0x16/0x68 > [ 7.620842][ T1] ? die+0x34/0x58 > [ 7.620842][ T1] ? do_trap+0x111/0x1e8 > [ 7.620842][ T1] ? do_basic_setup+0x5b/0x90 > [ 7.620842][ T1] ? do_error_trap+0x11a/0x190 > [ 7.620842][ T1] ? do_basic_setup+0x5b/0x90 > [ 7.620842][ T1] ? handle_invalid_op+0x34/0x50 > [ 7.620842][ T1] ? do_basic_setup+0x5b/0x90 > [ 7.620842][ T1] ? exc_invalid_op+0x32/0x48 > [ 7.620842][ T1] ? asm_exc_invalid_op+0x16/0x20 > [ 7.620842][ T1] ? __cfi_asan.module_ctor+0x10/0x10 > [ 7.620842][ T1] ? do_basic_setup+0x5b/0x90 > [ 7.620842][ T1] kernel_init_freeable+0xf0/0x190 > [ 7.620842][ T1] ? __cfi_kernel_init+0x8/0x8 > [ 7.620842][ T1] kernel_init+0x19/0x198 > [ 7.620842][ T1] ? __cfi_kernel_init+0x8/0x8 > [ 7.620842][ T1] ret_from_fork+0x5a/0x88 > [ 7.620842][ T1] ? __cfi_kernel_init+0x8/0x8 > [ 7.620842][ T1] ret_from_fork_asm+0x11/0x20 > [ 7.620842][ T1] </TASK> > [ 7.620842][ T1] Modules linked in: > [ 7.620846][ T1] ---[ end trace 0000000000000000 ]--- > [ 7.621487][ T1] RIP: 0010:do_basic_setup+0x5b/0x90 > [ 7.622107][ T1] Code: 00 fc ff df 48 89 d8 48 c1 e8 03 42 80 3c 38 00 74 08 48 89 df e8 6d 85 50 fb 4d 8b 5e f8 41 ba a0 82 3b 1a 45 03 53 fc 74 02 <0f> 0b 41 ff d3 49 81 fe 68 10 7e be 73 0f e8 8a eb 12 fb 48 83 c3 > [ 7.624206][ T1] RSP: 0000:ffffc9000001fed0 EFLAGS: 00010286 > [ 7.624847][ T1] RAX: 1ffffffff7cfb6de RBX: ffffffffbe7db6f0 RCX: 0000000000000000 > [ 7.625768][ T1] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 > [ 7.626696][ T1] RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 > [ 7.627602][ T1] R10: 00000000bf7be9ac R11: ffffffffbbdc9360 R12: ffffffffbd039fc0 > [ 7.628513][ T1] R13: 0000000000000000 R14: ffffffffbe7db6f8 R15: dffffc0000000000 > [ 7.629316][ T1] FS: 0000000000000000(0000) GS:ffffffffbd0dc000(0000) knlGS:0000000000000000 > [ 7.630979][ T1] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 > [ 7.632216][ T1] CR2: ffff88843ffff000 CR3: 000000042529e000 CR4: 00000000000406f0 > [ 7.633336][ T1] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 > [ 7.634842][ T1] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 > [ 7.636376][ T1] Kernel panic - not syncing: Fatal exception > > > -- > 0-DAY CI Kernel Test Service > https://github.com/intel/lkp-tests/wiki Hmm. This config has: CONFIG_CLANG_VERSION=190102 Sami, is the fix not available as of llvm 19? Alice
On Mon, Oct 28, 2024 at 1:34 AM Alice Ryhl <aliceryhl@google.com> wrote: > > Hmm. This config has: > > CONFIG_CLANG_VERSION=190102 > > Sami, is the fix not available as of llvm 19? Looks like llvmorg-19.1.2 doesn't have the fix, which means it won't be available until LLVM 20. :/ Sami
On Mon, Oct 28, 2024 at 4:15 PM Sami Tolvanen <samitolvanen@google.com> wrote: > > On Mon, Oct 28, 2024 at 1:34 AM Alice Ryhl <aliceryhl@google.com> wrote: > > > > Hmm. This config has: > > > > CONFIG_CLANG_VERSION=190102 > > > > Sami, is the fix not available as of llvm 19? > > Looks like llvmorg-19.1.2 doesn't have the fix, which means it won't > be available until LLVM 20. :/ It's not going to land in a patch release of llvm 19? Alice
On Mon, Oct 28, 2024 at 8:18 AM Alice Ryhl <aliceryhl@google.com> wrote: > > On Mon, Oct 28, 2024 at 4:15 PM Sami Tolvanen <samitolvanen@google.com> wrote: > > > > On Mon, Oct 28, 2024 at 1:34 AM Alice Ryhl <aliceryhl@google.com> wrote: > > > > > > Hmm. This config has: > > > > > > CONFIG_CLANG_VERSION=190102 > > > > > > Sami, is the fix not available as of llvm 19? > > > > Looks like llvmorg-19.1.2 doesn't have the fix, which means it won't > > be available until LLVM 20. :/ > > It's not going to land in a patch release of llvm 19? It won't land to 19.x automatically, but I requested a backport: https://github.com/llvm/llvm-project/pull/113938 Sami
On Mon, Oct 28, 2024 at 6:23 PM Sami Tolvanen <samitolvanen@google.com> wrote: > > On Mon, Oct 28, 2024 at 8:18 AM Alice Ryhl <aliceryhl@google.com> wrote: > > > > On Mon, Oct 28, 2024 at 4:15 PM Sami Tolvanen <samitolvanen@google.com> wrote: > > > > > > On Mon, Oct 28, 2024 at 1:34 AM Alice Ryhl <aliceryhl@google.com> wrote: > > > > > > > > Hmm. This config has: > > > > > > > > CONFIG_CLANG_VERSION=190102 > > > > > > > > Sami, is the fix not available as of llvm 19? > > > > > > Looks like llvmorg-19.1.2 doesn't have the fix, which means it won't > > > be available until LLVM 20. :/ > > > > It's not going to land in a patch release of llvm 19? > > It won't land to 19.x automatically, but I requested a backport: > https://github.com/llvm/llvm-project/pull/113938 Thanks! Looks like it already landed. Which patch version will it land in? Alice
On Tue, Oct 29, 2024 at 2:09 AM Alice Ryhl <aliceryhl@google.com> wrote: > > On Mon, Oct 28, 2024 at 6:23 PM Sami Tolvanen <samitolvanen@google.com> wrote: > > > > On Mon, Oct 28, 2024 at 8:18 AM Alice Ryhl <aliceryhl@google.com> wrote: > > > > > > On Mon, Oct 28, 2024 at 4:15 PM Sami Tolvanen <samitolvanen@google.com> wrote: > > > > > > > > On Mon, Oct 28, 2024 at 1:34 AM Alice Ryhl <aliceryhl@google.com> wrote: > > > > > > > > > > Hmm. This config has: > > > > > > > > > > CONFIG_CLANG_VERSION=190102 > > > > > > > > > > Sami, is the fix not available as of llvm 19? > > > > > > > > Looks like llvmorg-19.1.2 doesn't have the fix, which means it won't > > > > be available until LLVM 20. :/ > > > > > > It's not going to land in a patch release of llvm 19? > > > > It won't land to 19.x automatically, but I requested a backport: > > https://github.com/llvm/llvm-project/pull/113938 > > Thanks! Looks like it already landed. Which patch version will it land in? It should be in 19.1.3. Sami
On Tue, Oct 29, 2024 at 4:19 PM Sami Tolvanen <samitolvanen@google.com> wrote: > > On Tue, Oct 29, 2024 at 2:09 AM Alice Ryhl <aliceryhl@google.com> wrote: > > > > On Mon, Oct 28, 2024 at 6:23 PM Sami Tolvanen <samitolvanen@google.com> wrote: > > > > > > On Mon, Oct 28, 2024 at 8:18 AM Alice Ryhl <aliceryhl@google.com> wrote: > > > > > > > > On Mon, Oct 28, 2024 at 4:15 PM Sami Tolvanen <samitolvanen@google.com> wrote: > > > > > > > > > > On Mon, Oct 28, 2024 at 1:34 AM Alice Ryhl <aliceryhl@google.com> wrote: > > > > > > > > > > > > Hmm. This config has: > > > > > > > > > > > > CONFIG_CLANG_VERSION=190102 > > > > > > > > > > > > Sami, is the fix not available as of llvm 19? > > > > > > > > > > Looks like llvmorg-19.1.2 doesn't have the fix, which means it won't > > > > > be available until LLVM 20. :/ > > > > > > > > It's not going to land in a patch release of llvm 19? > > > > > > It won't land to 19.x automatically, but I requested a backport: > > > https://github.com/llvm/llvm-project/pull/113938 > > > > Thanks! Looks like it already landed. Which patch version will it land in? > > It should be in 19.1.3. Looking at https://github.com/llvm/llvm-project/commits/release/19.x/ it landed after commit 17365dfd2101 ("Bump version to 19.1.3"), so does that not mean it will land in 19.1.4? Or does the repository bump the version at the beginning of the version range rather than after? Alice
On Wed, Oct 30, 2024 at 10:47 AM Alice Ryhl <aliceryhl@google.com> wrote: > > On Tue, Oct 29, 2024 at 4:19 PM Sami Tolvanen <samitolvanen@google.com> wrote: > > > > On Tue, Oct 29, 2024 at 2:09 AM Alice Ryhl <aliceryhl@google.com> wrote: > > > > > > On Mon, Oct 28, 2024 at 6:23 PM Sami Tolvanen <samitolvanen@google.com> wrote: > > > > > > > > On Mon, Oct 28, 2024 at 8:18 AM Alice Ryhl <aliceryhl@google.com> wrote: > > > > > > > > > > On Mon, Oct 28, 2024 at 4:15 PM Sami Tolvanen <samitolvanen@google.com> wrote: > > > > > > > > > > > > On Mon, Oct 28, 2024 at 1:34 AM Alice Ryhl <aliceryhl@google.com> wrote: > > > > > > > > > > > > > > Hmm. This config has: > > > > > > > > > > > > > > CONFIG_CLANG_VERSION=190102 > > > > > > > > > > > > > > Sami, is the fix not available as of llvm 19? > > > > > > > > > > > > Looks like llvmorg-19.1.2 doesn't have the fix, which means it won't > > > > > > be available until LLVM 20. :/ > > > > > > > > > > It's not going to land in a patch release of llvm 19? > > > > > > > > It won't land to 19.x automatically, but I requested a backport: > > > > https://github.com/llvm/llvm-project/pull/113938 > > > > > > Thanks! Looks like it already landed. Which patch version will it land in? > > > > It should be in 19.1.3. > > Looking at > https://github.com/llvm/llvm-project/commits/release/19.x/ > > it landed after commit 17365dfd2101 ("Bump version to 19.1.3"), so > does that not mean it will land in 19.1.4? Or does the repository bump > the version at the beginning of the version range rather than after? I guess they just don't synchronize the bump with the release. It is both under the tag and listed on https://discourse.llvm.org/t/llvm-19-1-3-relased/82829 Alice
© 2016 - 2024 Red Hat, Inc.