public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/107361] Why does -Wclass-memaccess require trivial types, instead of trivially-copyable types? Date: Sun, 23 Oct 2022 23:52:32 +0000 [thread overview] Message-ID: <bug-107361-4-t6hbaKv6H6@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107361-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107361 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- https://gcc.gnu.org/legacy-ml/gcc-patches/2017-04/msg01571.html
next prev parent reply other threads:[~2022-10-23 23:52 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-23 7:22 [Bug c++/107361] New: " carlosgalvezp at gmail dot com 2022-10-23 23:52 ` pinskia at gcc dot gnu.org [this message] 2022-10-24 6:19 ` [Bug c++/107361] " carlosgalvezp at gmail dot com 2024-05-28 15:33 ` pkasting at google 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-107361-4-t6hbaKv6H6@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).