On Wed, Mar 19, 2025 at 7:55 AM Alexei Starovoitov <alexei.starovoitov@xxxxxxxxx> wrote: > > On Wed, Mar 19, 2025 at 7:36 AM Kumar Kartikeya Dwivedi > <memxor@xxxxxxxxx> wrote: > > > > > > > > > > I've sent a fix [0], but unfortunately I was unable to reproduce the > > > > problem with an LLVM >= 19 build, idk why. I will try with GCC >= 14 > > > > as the patches require to confirm, but based on the error I am 99% > > > > sure it will fix the problem. > > > > > > Probably because __seg_gs has CC_HAS_NAMED_AS depends on CC_IS_GCC. > > > Let me give it a go with GCC. > > > > > > > Can confirm now that this fixes it, I just did a build with GCC 14 > > where Uros's __percpu checks kick in. > > Great. Thanks for checking and quick fix. > > btw clang supports it with __attribute__((address_space(256))), > so CC_IS_GCC probably should be relaxed. Stephen, bpf-next/for-next is force pushed with the fix. Thank you for flagging it quickly! Appreciate it.
