public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "raanan.lori at getnexar dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/115160] Enabling undefined behaviour sanitizer causes or'ed bit shift to report wrong result Date: Tue, 21 May 2024 09:41:36 +0000 [thread overview] Message-ID: <bug-115160-4-N9dcAL7qAJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115160-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115160 --- Comment #2 from Ra'anan Lori <raanan.lori at getnexar dot com> --- it's sad to see this response, since the major issue here is that a user that wants to use the undefined behaviour sanitizer in such a case will not only get no warning but also still have the UB and will get a changed value because of it the "bogus" test case, is simplified example from a much bigger code base that illustrates the exact issue. i would expect that a detection for cpp code (instead of raw c) would also catch the UB, but it seems it won't. so i would at least expect the UB sanitizer to warn against not really working when used with cpp code.
next prev parent reply other threads:[~2024-05-21 9:41 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-20 10:03 [Bug c++/115160] New: " raanan.lori at getnexar dot com 2024-05-20 17:56 ` [Bug c++/115160] " jakub at gcc dot gnu.org 2024-05-21 9:41 ` raanan.lori at getnexar dot com [this message] 2024-05-21 9:53 ` jakub at gcc dot gnu.org 2024-05-21 10:07 ` raanan.lori at getnexar dot com 2024-05-21 11:46 ` redi at gcc dot gnu.org 2024-05-21 12:09 ` 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-115160-4-N9dcAL7qAJ@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).