public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dlong at cadence dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/103519] New: Address sanitizer check missing for AVX512 masked load Date: Wed, 01 Dec 2021 14:43:36 +0000 [thread overview] Message-ID: <bug-103519-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103519 Bug ID: 103519 Summary: Address sanitizer check missing for AVX512 masked load Product: gcc Version: 11.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: sanitizer Assignee: unassigned at gcc dot gnu.org Reporter: dlong at cadence dot com CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org, jakub at gcc dot gnu.org, kcc at gcc dot gnu.org, marxin at gcc dot gnu.org Target Milestone: --- Example with generated assembly available here: https://godbolt.org/z/WTo5sGThb In this: #include <x86intrin.h> __m512d v; void access(float const *addr) { __m512d val; __m256 val1; __mmask8 const k3 = 0x3f; val1=_mm256_maskz_loadu_ps(k3, addr); val=_mm512_cvtps_pd(val1); _mm512_storeu_pd((double *)&v, val); } when compiled with AVX512 instructions and -fsanitize=address, no address check is generated for the maskz_load. (FWIW, if the mask is folded into the conversion using maskz_cvtps_pd instead then a check is generated. However it's a check for a full 32-byte access even though the CPU will only actually access 24-bytes due to the mask.)
next reply other threads:[~2021-12-01 14:43 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-01 14:43 dlong at cadence dot com [this message] 2021-12-01 14:52 ` [Bug sanitizer/103519] " dlong at cadence dot com 2021-12-02 1:27 ` crazylht at gmail dot com 2021-12-02 10:54 ` rguenth at gcc dot gnu.org 2021-12-02 11:55 ` 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-103519-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).