ABataev added a comment. I don't think this kind of analysis must be here. clang has a special analysis phase, maybe better to implement it there? Currently, it may produce false-positive warnings. Also, why only check for array accesses? Are they the only constructs that may lead to undefined behavior?
================ Comment at: clang/include/clang/Basic/DiagnosticSemaKinds.td:9269 +def warn_omp_atomic_evaluation_times_undefined : Warning< + "the number of times the expression evaluated is unspecified">; def err_omp_invalid_target_decl : Error< ---------------- Hmm, the message does not say anything about the real problem. Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D71294/new/ https://reviews.llvm.org/D71294 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
