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 libgcc/114689] New: [14 Regression] libgcc/config/m68k/fpgnulib.c:305: Suspicious coding ? Date: Thu, 11 Apr 2024 09:00:47 +0000 [thread overview] Message-ID: <bug-114689-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114689 Bug ID: 114689 Summary: [14 Regression] libgcc/config/m68k/fpgnulib.c:305: Suspicious coding ? Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libgcc Assignee: unassigned at gcc dot gnu.org Reporter: dcb314 at hotmail dot com Target Milestone: --- Static analyser cppcheck says: libgcc/config/m68k/fpgnulib.c:305:37: style: Boolean result is used in bitwise operation. Clarify expression with parentheses. [clarifyCondition] Source code is mant = mant >> 1 | (mant & 1) | !!sticky; Perhaps mant = (mant >> 1) | (mant & 1) | !!sticky; was intended. This problem doesn't exist in the source code of gcc-13.2
next reply other threads:[~2024-04-11 9:00 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-11 9:00 dcb314 at hotmail dot com [this message] 2024-04-11 10:35 ` [Bug libgcc/114689] " rguenth at gcc dot gnu.org 2024-04-12 8:30 ` jakub at gcc dot gnu.org 2024-04-12 10:13 ` schwab@linux-m68k.org 2024-04-12 10:16 ` jakub at gcc dot gnu.org 2024-04-12 13:33 ` law at gcc dot gnu.org 2024-04-12 21:47 ` dcb314 at hotmail dot com 2024-04-12 21:56 ` jakub at gcc dot gnu.org 2024-04-13 7:06 ` dcb314 at hotmail dot com 2024-04-15 15:46 ` cvs-commit 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-114689-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).