public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "thomas at habets dot se" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/103881] Wconversion false positive when using |= and &= with two rvalues in binary op Date: Sun, 02 Jan 2022 12:35:38 +0000 [thread overview] Message-ID: <bug-103881-4-JzpMRfFcRY@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103881-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103881 --- Comment #3 from thomas at habets dot se --- Interesting. So the difference between "x |= a & a" and "x |= f() & f()" is that the latter has passed a somewhat arbitrary level of complexity after which GCC is not able to prove that it's safe, and therefore warns as it being potentially losing precision? It's understandable, but unfortunate. It means that I have no hope of having real world programs be free of false positives for conversion warnings.
next prev parent reply other threads:[~2022-01-02 12:35 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-31 16:46 [Bug c/103881] New: " thomas at habets dot se 2021-12-31 17:36 ` [Bug c/103881] " thomas at habets dot se 2021-12-31 17:48 ` jakub at gcc dot gnu.org 2022-01-02 12:35 ` thomas at habets dot se [this message] 2022-01-11 18:15 ` cvs-commit at gcc dot gnu.org 2022-01-20 3:58 ` egallager at gcc dot gnu.org 2022-01-20 14:56 ` thomas at habets dot se 2022-01-24 9:21 ` cvs-commit at gcc dot gnu.org 2022-05-10 8:22 ` cvs-commit at gcc dot gnu.org 2022-05-10 15:31 ` 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-103881-4-JzpMRfFcRY@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).