On Fri, 10 Apr 2026 at 04:10, Harry Yoo (Oracle) <[email protected]> wrote: [...] > > Which is sad, because that means we need the macro workaround. > > > > Do you want to be credited with Co-authored-by > > I'd appreciate that. (I guess you meant Co-developed-by)
Thanks (and yes). > > - in which case I need your Signed-off-by. > > Signed-off-by: Harry Yoo (Oracle) <[email protected]> > > > > Not sure if it's safe to do that for exported functions though (since > > > modules can be built w/ a different compiler). > > > > Kernel modules built with a different config (implicit if different > > compiler) are not supported, and never have been. If it works, it's > > just luck (I know people do this, but it's just a disaster waiting to > > happen). > > And if GCC folks somehow fix this at some point, even kernel modules > built with a different version of GCC might not be supported? Yes, and different compiler version also implies different compiler (so even GCC A.B != GCC X.Y), because newer compiler versions may activate different codegen options (some of which we auto-enable if available).
