public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "chip at pobox dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/54585] stack space allocated but never used when calling functions that return structs in registers Date: Mon, 23 Sep 2013 20:05:00 -0000 [thread overview] Message-ID: <bug-54585-4-oeWQw5ZiUb@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54585-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54585 --- Comment #3 from Chip Salzenberg <chip at pobox dot com> --- It's worth it for cache reasons I believe. The data cache works better you don't spread out the stack data unnecessarily. More concretely, if the stack frame can entirely disappear then you also reduce the instruction count. That's fewer instructions to dispatch and less icache pressure.
next prev parent reply other threads:[~2013-09-23 20:05 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-09-14 21:11 [Bug rtl-optimization/54585] New: " chip at pobox dot com 2013-09-05 20:06 ` [Bug rtl-optimization/54585] " chip at pobox dot com 2013-09-05 21:05 ` ebotcazou at gcc dot gnu.org 2013-09-23 20:05 ` chip at pobox dot com [this message] 2021-12-18 23:59 ` [Bug middle-end/54585] " pinskia 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-54585-4-oeWQw5ZiUb@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).