https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94362
--- Comment #6 from CVS Commits ---
The master branch has been updated by David Malcolm :
https://gcc.gnu.org/g:e966a508e03fe28bfca65a1e60e579fa90355ea6
commit r12-6875-ge966a508e03fe28bfca65a1e60e579fa90355ea6
Author: David Malcolm
Date: Tu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94362
David Malcolm changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94362
--- Comment #4 from CVS Commits ---
The master branch has been updated by David Malcolm :
https://gcc.gnu.org/g:c4b8f3730a80025192fdb485ad2535c165340e41
commit r12-6782-gc4b8f3730a80025192fdb485ad2535c165340e41
Author: David Malcolm
Date: Th
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94362
--- Comment #3 from David Malcolm ---
The root cause is that the analyzer's path feasibility checker erroneously
considers this to be feasible:
(R + 1 > 0) && (R < 0)
for int R (the return value from sk_EVP_PKEY_ASN1_METHOD_num), whereas it's n
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94362
--- Comment #2 from David Malcolm ---
Oops; I was wrong; this isn't yet fixed on trunk. I can reproduce this with
the attachment. It also reports warnings from -Wanalyzer-too-complex.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94362
David Malcolm changed:
What|Removed |Added
Last reconfirmed||2021-02-17
Status|UNCONFIRME
