public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/89863] [meta-bug] Issues in gcc that other static analyzers (cppcheck, clang-static-analyzer, PVS-studio) find that gcc misses Date: Tue, 05 May 2020 14:01:24 +0000 [thread overview] Message-ID: <bug-89863-4-uRsXqYH2T8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-89863-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89863 Bug 89863 depends on bug 89860, which changed state. Bug 89860 Summary: liboffloadmic/runtime/offload_target.cpp:332]: (style) Array index 'i' is used before limits check. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89860 What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED
next prev parent reply other threads:[~2020-05-05 14:01 UTC|newest] Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-89863-4@http.gcc.gnu.org/bugzilla/> 2020-04-03 15:21 ` [Bug other/89863] [meta-bug] Issues that static analyzers (cppcheck, clang-static-analyzer) " sripar01 at gcc dot gnu.org 2020-04-17 9:23 ` [Bug other/89863] [meta-bug] Issues in gcc that other static analyzers (cppcheck, clang-static-analyzer, PVS-studio) " egallager at gcc dot gnu.org 2020-04-17 9:28 ` egallager at gcc dot gnu.org 2020-04-20 13:24 ` jakub at gcc dot gnu.org 2020-05-05 14:00 ` marxin at gcc dot gnu.org 2020-05-05 14:01 ` marxin at gcc dot gnu.org 2020-05-05 14:01 ` marxin at gcc dot gnu.org [this message] 2020-09-29 14:32 ` dmalcolm at gcc dot gnu.org 2020-11-06 22:17 ` egallager at gcc dot gnu.org 2020-11-06 22:17 ` egallager at gcc dot gnu.org 2020-11-06 22:18 ` egallager at gcc dot gnu.org 2021-03-13 4:29 ` ian at airs dot com 2021-03-18 9:44 ` marxin at gcc dot gnu.org 2021-03-19 13:09 ` dmalcolm at gcc dot gnu.org 2021-04-06 17:44 ` ibuclaw at gdcproject dot org 2021-04-09 11:46 ` rsandifo at gcc dot gnu.org 2021-05-10 7:21 ` marxin at gcc dot gnu.org 2021-05-13 12:17 ` marxin at gcc dot gnu.org 2021-06-14 14:57 ` burnus at gcc dot gnu.org 2021-08-24 19:41 ` pinskia at gcc dot gnu.org 2021-09-15 20:39 ` pinskia at gcc dot gnu.org 2021-10-04 9:20 ` charlet at gcc dot gnu.org 2021-11-12 15:02 ` marxin at gcc dot gnu.org 2021-11-15 0:12 ` egallager at gcc dot gnu.org 2022-01-05 18:26 ` redi at gcc dot gnu.org 2022-01-16 1:16 ` rodgertq at gcc dot gnu.org 2022-07-07 5:58 ` mir at gcc dot gnu.org 2022-08-31 9:51 ` jakub at gcc dot gnu.org 2022-11-03 10:22 ` ams at gcc dot gnu.org 2022-11-04 10:58 ` tschwinge at gcc dot gnu.org 2023-06-05 7:21 ` pinskia at gcc dot gnu.org 2024-01-17 21:19 ` jamborm at gcc dot gnu.org 2024-02-08 21:50 ` redi at gcc dot gnu.org 2024-02-27 15:26 ` jeevitha at gcc dot gnu.org 2024-04-15 15:48 ` jakub at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-89863-4-uRsXqYH2T8@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).