rjmccall added a comment. Does LLVM model `noinline` as a call-site attribute in the way that would be necessary to get that effect? Also, are you actually having a problem here, or is this just something you noticed in the code?
I'm not sure we can warn about putting the attribute on a declaration; it's presumably still picked up by later definitions. There's probably a warning if they conflict, as they would if the first declaration was in a header included in both places, which is best practice. Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D108618/new/ https://reviews.llvm.org/D108618 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
