On Wed, Oct 21, 2026 at 4:21 PM Giuliano Procida <[email protected]> wrote: > > The description was AI generated, but it is accurate. Both paths use the > triple-underscore three-argument macro alone.
Yeah, I understand that not having the `extern` and so on is what the AI wants to emphasize here, instead of the `asm(...` wrapping of the `#else` side, but it sounds confusing to me, i.e. it introduces the change as if matching the assembly path was important for some reason in particular. > I wondered the same thing, but that would introduce yet another intermediate > macro. We are introducing a macro either way -- in fact we have to introduce it twice if we don't do it centrally. I guess you mean avoiding the duplication in the C header, but that duplication already exists in this version. So if no new intermediate macro is preferred, then at least the duplication would be more local and thus more obvious when they both need to be updated. > No, Android kernels have been built with Clang for years. > > We post-process DWARF information with STG for ABI purposes and noticed > this interesting side effect there. Ah, nevermind, I checked the DWARF emitted by Clang, but without gendwarfksyms, my bad (I am aware of Android using Clang, of course; it is why it sounded strange and wanted to double-check if it was related to GCC somehow). Thanks! Cheers, Miguel
