public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/50883] [ARM] Suboptimal optimization for small structures Date: Fri, 04 Feb 2022 12:29:13 +0000 [thread overview] Message-ID: <bug-50883-4-n5LJUIJqel@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50883-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50883 --- Comment #16 from Richard Earnshaw <rearnsha at gcc dot gnu.org> --- And there are also cases where we end up with dead stack slots which can't be removed, so there's a stack size impact as well.
next prev parent reply other threads:[~2022-02-04 12:29 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-10-27 11:55 [Bug target/50883] New: " sebastian.huber@embedded-brains.de 2011-10-27 11:56 ` [Bug target/50883] " sebastian.huber@embedded-brains.de 2011-10-27 11:58 ` sebastian.huber@embedded-brains.de 2011-10-27 11:58 ` sebastian.huber@embedded-brains.de 2011-10-27 14:51 ` rguenth at gcc dot gnu.org 2011-10-27 15:20 ` sebastian.huber@embedded-brains.de 2011-10-27 16:53 ` rearnsha at gcc dot gnu.org 2022-02-04 0:50 ` pinskia at gcc dot gnu.org 2022-02-04 0:50 ` pinskia at gcc dot gnu.org 2022-02-04 11:05 ` rearnsha at gcc dot gnu.org 2022-02-04 11:11 ` pinskia at gcc dot gnu.org 2022-02-04 11:30 ` rguenth at gcc dot gnu.org 2022-02-04 11:45 ` ebotcazou at gcc dot gnu.org 2022-02-04 11:58 ` rguenther at suse dot de 2022-02-04 12:24 ` ebotcazou at gcc dot gnu.org 2022-02-04 12:27 ` rearnsha at gcc dot gnu.org 2022-02-04 12:29 ` rearnsha at gcc dot gnu.org [this message] 2022-02-04 12:55 ` ebotcazou at gcc dot gnu.org 2022-02-04 16:29 ` sebastian.huber@embedded-brains.de
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-50883-4-n5LJUIJqel@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).