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 c++/94923] False positive -Wclass-memaccess with trivially copyable std::optional Date: Tue, 19 May 2020 19:09:04 +0000 [thread overview] Message-ID: <bug-94923-4-A3upZZzFkK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94923-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94923 --- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Martin Sebor <msebor@gcc.gnu.org>: https://gcc.gnu.org/g:c0d8623ce5aa6d92c2e6c62e1bee66272a011f59 commit r11-499-gc0d8623ce5aa6d92c2e6c62e1bee66272a011f59 Author: Martin Sebor <msebor@redhat.com> Date: Tue May 19 12:46:37 2020 -0600 PR c++/94923 - False positive -Wclass-memaccess with trivially copyable std::optional gcc/cp/ChangeLog: PR c++/94923 * call.c ((maybe_warn_class_memaccess): Use is_byte_access_type. * cp-tree.h (is_dummy_object): Return bool. (is_byte_access_type): Declare new function. * tree.c (is_dummy_object): Return bool. (is_byte_access_type): Define new function. gcc/testsuite/ChangeLog: PR c++/94923 * g++.dg/Wclass-memaccess.C: Add tests for std::byte.
next prev parent reply other threads:[~2020-05-19 19:09 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-02 13:46 [Bug c++/94923] New: " dawid_jurek at vp dot pl 2020-05-02 15:38 ` [Bug c++/94923] " daniel.kruegler at googlemail dot com 2020-05-02 17:59 ` dawid_jurek at vp dot pl 2020-05-02 22:34 ` msebor at gcc dot gnu.org 2020-05-02 22:36 ` msebor at gcc dot gnu.org 2020-05-08 18:58 ` msebor at gcc dot gnu.org 2020-05-19 19:09 ` cvs-commit at gcc dot gnu.org [this message] 2020-05-21 8:31 ` dawid_jurek at vp dot pl 2022-03-17 19:53 ` msebor 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-94923-4-A3upZZzFkK@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).