public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jzwinck at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/107298] New: Failure to compile code with std::optional and ASan/UBSan Date: Mon, 17 Oct 2022 15:01:54 +0000 [thread overview] Message-ID: <bug-107298-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107298 Bug ID: 107298 Summary: Failure to compile code with std::optional and ASan/UBSan Product: gcc Version: 12.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: sanitizer Assignee: unassigned at gcc dot gnu.org Reporter: jzwinck at gmail 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: --- Test case which is expected to compile: #include <optional> std::optional<bool> f(bool cond) { if (cond) { return std::make_optional(true); } return {}; } bool g() { return *f(true); } GCC 10, 11 and 12 all fail to compile this with "-Wall -Wextra -Werror -O2 -fsanitize=undefined": error: '*(unsigned char*)((char*)&<unnamed> + offsetof(std::optional<bool>,std::optional<bool>::<unnamed>.std::_Optional_base<bool, true, true>::<unnamed>))' may be used uninitialized [-Werror=maybe-uninitialized] return {}; Removing std::make_optional or replacing it with std::optional<bool> makes the error go away, though these changes should be irrelevant since they're not on the code path the compiler complains about. Compiling without a sanitizer also works fine. Demo: https://godbolt.org/z/TafE9cxWW
next reply other threads:[~2022-10-17 15:01 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-17 15:01 jzwinck at gmail dot com [this message] 2022-10-17 19:24 ` [Bug sanitizer/107298] " marxin at gcc dot gnu.org 2022-10-17 19:24 ` marxin at gcc dot gnu.org 2022-10-18 7:18 ` jzwinck at gmail dot com 2022-10-19 7:19 ` marxin at gcc dot gnu.org 2022-10-28 7:16 ` cvs-commit 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-107298-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).