On Sun, Jan 26, 2025 at 8:46 PM Uros Bizjak <ubizjak@xxxxxxxxx> wrote: > > On Sun, Jan 26, 2025 at 7:30 PM Linus Torvalds > <torvalds@xxxxxxxxxxxxxxxxxxxx> wrote: > > > That does seem to work, but I'd admittedly be happier if we could just > > find some way to dynamically disable/enable __typeof_unqual__ based on > > which compiler is used, rather than make it a config option. So that > > bindgen would not see it, but a recent enough C compiler would. > > > > We already use '__has_attribute()' for some of these things. There's a > > '__has_extension()' thing that comes from clang but that gcc also > > supports. > > > > But I can't find the list of extensions that that model supports, and > > I guess typeof_unqual isn't on that list if I find it. Sorry, I sent the previous message too fast. Unfortunately, you are right. The following doesn't trigger #error neither with gcc, neither with clang: #if __has_extension (__typeof_unqual__) # error #endif Uros.