https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108189
--- Comment #9 from James Hilliard <james.hilliard1 at gmail dot com> --- (In reply to Andrew Pinski from comment #5) > Also Clang does not implement this warning at all. > > It is a bug in bpf-next really. What would be the correct way to fix these in bpf-next?