Open Quuxplusone opened 3 years ago
Bugzilla Link | PR48482 |
Status | CONFIRMED |
Importance | P normal |
Reported by | Dmitry Polukhin (dmitry.polukhin@gmail.com) |
Reported on | 2020-12-11 04:17:50 -0800 |
Last modified on | 2020-12-30 15:22:48 -0800 |
Version | trunk |
Hardware | All All |
CC | balazs.benics@sigmatechnology.se, dcoughlin@apple.com, dkszelethus@gmail.com, llvm-bugs@lists.llvm.org, mtekieli@gmail.com, noqnoqneo@gmail.com, xazax.hun@gmail.com |
Fixed by commit(s) | |
Attachments | |
Blocks | |
Blocked by | |
See also |
Uh-oh, yeah, this is clearly broken.
This false positive is caused by presence of a seemingly unrelated checker in your run-line, namely optin.cplusplus.UninitializedObject. If you explicitly disable this checker the false positive goes away.
Looks like one of the two checkers performs transitions incorrectly which causes a sudden state split near the exit from Number::Number.
Thanks for the bug report, I'll investigate further.
_Bug 48633 has been marked as a duplicate of this bug._
In https://bugs.llvm.org/show_bug.cgi?id=48633 there are a couple more examples of false positives in other checkers with the same root cause.