The total number of evaluation of X is undefined for atomic construct,
therefore, we emit warning message for them. BTW, Clang is always
evaluate X once.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
- Build Status
Buildable 42236 Build 42660: arc lint + arc unit
Event Timeline
Comment Actions
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?
clang/include/clang/Basic/DiagnosticSemaKinds.td | ||
---|---|---|
9269 | Hmm, the message does not say anything about the real problem. |
Hmm, the message does not say anything about the real problem.