public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/113528] New: gcc-13 meets PVS-studio Date: Sun, 21 Jan 2024 08:10:02 +0000 [thread overview] Message-ID: <bug-113528-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113528 Bug ID: 113528 Summary: gcc-13 meets PVS-studio Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: dcb314 at hotmail dot com Target Milestone: --- The following article describes using static analyser PVS-studio to find potential problems in gcc-13. https://pvs-studio.com/en/blog/posts/cpp/1067/ It might be worth checking the ten problems listed. It might also be worth checking that gcc trunk has no new problems, compared to gcc-13.
next reply other threads:[~2024-01-21 8:10 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-21 8:10 dcb314 at hotmail dot com [this message] 2024-01-21 8:36 ` [Bug middle-end/113528] " pinskia at gcc dot gnu.org 2024-01-21 8:49 ` pinskia at gcc dot gnu.org 2024-01-21 8:55 ` pinskia 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-113528-4@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).