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/107250] New: Load unnecessarily happens before malloc Date: Thu, 13 Oct 2022 14:54:19 +0000 [thread overview] Message-ID: <bug-107250-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107250 Bug ID: 107250 Summary: Load unnecessarily happens before malloc 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: --- The following code will be compiled with the load of next happening before the call to malloc. This generates worse code than if the load is delayed until after the call to malloc. struct Foo { Foo* next; }; void ctx_push(Foo* f) { Foo tmp = { f->next }; Foo *n = (Foo*)malloc(sizeof(Foo)); *n = tmp; f->next = n; } Manually moving the load in this example improves the generated code: struct Foo { Foo* next; }; void ctx_push(Foo* f) { Foo *n = (Foo*)malloc(sizeof(Foo)); Foo tmp = { f->next }; *n = tmp; f->next = n; } https://gcc.godbolt.org/z/TnMj1c636
next reply other threads:[~2022-10-13 14:54 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-13 14:54 jmuizelaar at mozilla dot com [this message] 2022-10-13 16:04 ` [Bug tree-optimization/107250] " amonakov at gcc dot gnu.org 2022-10-14 7:37 ` [Bug target/107250] " rguenth at gcc dot gnu.org 2022-10-14 7:55 ` amonakov 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-107250-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).