public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/107837] [10/11/12/13 Regression] Missed optimization: Using memcpy to load a struct unnecessary uses stack space since r8-5200 Date: Fri, 02 Dec 2022 10:58:40 +0000 [thread overview] Message-ID: <bug-107837-4-Cy61MSrvIK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107837-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107837 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org, | |jamborm at gcc dot gnu.org Priority|P3 |P2 Keywords|needs-bisection | Summary|[10/11/12/13 Regression] |[10/11/12/13 Regression] |Missed optimization: Using |Missed optimization: Using |memcpy to load a struct |memcpy to load a struct |unnecessary uses stack |unnecessary uses stack |space |space since r8-5200 --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Started with r8-5200-gd90ffcfb7d105d004cf04911a42935be03256b49
next prev parent reply other threads:[~2022-12-02 10:58 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-23 15:23 [Bug tree-optimization/107837] New: Missed optimization: Using memcpy to load a struct unnecessary uses stack space chfast at gmail dot com 2022-11-23 18:06 ` [Bug tree-optimization/107837] [10/11/12/13 Regression] " pinskia at gcc dot gnu.org 2022-12-02 10:58 ` jakub at gcc dot gnu.org [this message] 2023-07-07 10:44 ` [Bug tree-optimization/107837] [11/12/13/14 Regression] Missed optimization: Using memcpy to load a struct unnecessary uses stack space since r8-5200 rguenth 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-107837-4-Cy61MSrvIK@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).