public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/115172] Invalid -fsanitize=bool sanitization of variable from named address space Date: Tue, 28 May 2024 17:09:08 +0000 [thread overview] Message-ID: <bug-115172-4-0dglNSS6hT@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115172-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115172 --- Comment #12 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-12 branch has been updated by Uros Bizjak <uros@gcc.gnu.org>: https://gcc.gnu.org/g:da9b7a507ef38287cc16bc88e808293019f9f531 commit r12-10477-gda9b7a507ef38287cc16bc88e808293019f9f531 Author: Jakub Jelinek <jakub@redhat.com> Date: Wed May 22 09:12:28 2024 +0200 ubsan: Use right address space for MEM_REF created for bool/enum sanitization [PR115172] The following testcase is miscompiled, because -fsanitize=bool,enum creates a MEM_REF without propagating there address space qualifiers, so what should be normally loaded using say %gs:/%fs: segment prefix isn't. Together with asan it then causes that load to be sanitized. 2024-05-22 Jakub Jelinek <jakub@redhat.com> PR sanitizer/115172 * ubsan.cc (instrument_bool_enum_load): If rhs is not in generic address space, use qualified version of utype with the right address space. Formatting fix. * gcc.dg/asan/pr115172.c: New test. (cherry picked from commit d3c506eff54fcbac389a529c2e98da108a410b7f)
next prev parent reply other threads:[~2024-05-28 17:09 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-21 9:33 [Bug sanitizer/115172] New: " ubizjak at gmail dot com 2024-05-21 10:05 ` [Bug sanitizer/115172] " jakub at gcc dot gnu.org 2024-05-21 10:16 ` jakub at gcc dot gnu.org 2024-05-21 10:20 ` ubizjak at gmail dot com 2024-05-21 10:35 ` jakub at gcc dot gnu.org 2024-05-21 14:21 ` ubizjak at gmail dot com 2024-05-21 17:19 ` pchelkin at ispras dot ru 2024-05-21 21:08 ` jakub at gcc dot gnu.org 2024-05-22 7:13 ` cvs-commit at gcc dot gnu.org 2024-05-22 7:19 ` cvs-commit at gcc dot gnu.org 2024-05-22 7:35 ` cvs-commit at gcc dot gnu.org 2024-05-22 11:11 ` jakub at gcc dot gnu.org 2024-05-28 17:09 ` cvs-commit at gcc dot gnu.org [this message] 2024-05-28 17:09 ` cvs-commit at gcc dot gnu.org 2024-05-28 17:11 ` ubizjak at gmail dot com
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-115172-4-0dglNSS6hT@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).