yaxunl added a comment. In https://reviews.llvm.org/D53153#1263771, @scott.linder wrote:
> The rationale is that `-fvisibility` only affects the default, and already > does not apply in many cases. For example, see the rest of the conditions > above the fvisibility check in `getLVForNamespaceScopeDecl`: when > `Var->getStorageClass() == SC_Static` the linkage is (usually) internal and > the visibility is default. In cases where individual symbols need unique > visibility an `__attribute__` can be used. > > I think one question is whether OpenCL language semantics allow us to make > these visibility determinations; I am going off of the APIs available to > access symbols. I feel confused. So -fvisibility only applies to situations where it does not cause conflicts with language rule enforced linkage/visibility? https://reviews.llvm.org/D53153 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
