public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/113528] gcc-13 meets PVS-studio Date: Sun, 21 Jan 2024 08:36:06 +0000 [thread overview] Message-ID: <bug-113528-4-8yr24yYgSl@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113528-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113528 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- > Fragment N4 Is NOT an issue, based on all of the uses of add_char, the character is tested before adding it ... And there 256 can hold all values of signed char. >Fragment N5 Is just a small codiing style issue and actually will be optimized directly to the same thing really in this case as ' ' and '+' test bit will be in the same word (the second word/element). >Fragment N7 Not a bug, was done on purpose, see r5-958-ga33ad58be16a52 (PR 61242 and https://gcc.gnu.org/pipermail/gcc-patches/2014-May/389815.html). > Fragment N8 This code is software generated and the length is 0 in the GTY marker: ctf_dvdef_t ** GTY ((length ("0"))) ctfc_vars_list; So not a bug. > Fragment N9 Looks to be a way to avoid a goto, maybe now we could use a lamdba instead. So just a coding style issue. I have not looked into the other ones yet.
next prev parent reply other threads:[~2024-01-21 8:36 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-21 8:10 [Bug c/113528] New: " dcb314 at hotmail dot com 2024-01-21 8:36 ` pinskia at gcc dot gnu.org [this message] 2024-01-21 8:49 ` [Bug middle-end/113528] " 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-8yr24yYgSl@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).