public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jmuizelaar at mozilla dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/107263] New: Memcpy not elided when initializing struct Date: Fri, 14 Oct 2022 13:13:28 +0000 [thread overview] Message-ID: <bug-107263-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107263 Bug ID: 107263 Summary: Memcpy not elided when initializing struct Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: jmuizelaar at mozilla dot com Target Milestone: --- With the following code struct Foo { Foo* next; char arr[580]; }; void ctx_push(Foo* f) { Foo tmp = { f->next }; *f = tmp; } Clang is able to generate code that just memsets `arr`. GCC instead initializes the entire struct on the stack and then copies it into `f`. https://gcc.godbolt.org/z/Yzcbs4G71
next reply other threads:[~2022-10-14 13:13 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-14 13:13 jmuizelaar at mozilla dot com [this message] 2022-10-14 15:45 ` [Bug tree-optimization/107263] " pinskia at gcc dot gnu.org 2022-10-17 7:43 ` rguenth at gcc dot gnu.org 2022-10-17 13:28 ` jmuizelaar at mozilla dot com 2024-03-19 17:27 ` hiraditya at msn 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-107263-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).