public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "carrot at google dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/40657] allocate local variables with fewer instructions Date: Tue, 07 Jul 2009 06:45:00 -0000 [thread overview] Message-ID: <20090707064455.16309.qmail@sourceware.org> (raw) In-Reply-To: <bug-40657-17659@http.gcc.gnu.org/bugzilla/> ------- Comment #5 from carrot at google dot com 2009-07-07 06:44 ------- Could we do the optimization in function thumb1_expand_prologue? If we find this opportunity in function thumb1_expand_prologue, we can remove the sp manipulations from prologue and epilogue. We also should add extra registers to push/pop operands. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40657
next prev parent reply other threads:[~2009-07-07 6:45 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-07-06 8:16 [Bug target/40657] New: " carrot at google dot com 2009-07-06 8:16 ` [Bug target/40657] " carrot at google dot com 2009-07-06 9:14 ` steven at gcc dot gnu dot org 2009-07-06 9:55 ` ramana at gcc dot gnu dot org 2009-07-06 10:43 ` steven at gcc dot gnu dot org 2009-07-07 6:45 ` carrot at google dot com [this message] 2009-07-13 14:23 ` rearnsha at arm dot com 2009-12-22 22:53 ` ramana at gcc dot gnu dot org 2010-03-31 21:42 ` bernds at codesourcery dot com 2010-04-27 9:34 ` bernds at gcc dot gnu dot org 2010-04-27 9:36 ` bernds at gcc dot gnu dot org 2010-07-02 17:41 ` carrot at google dot com 2010-07-09 9:03 ` bernds at gcc dot gnu dot org [not found] <bug-40657-4@http.gcc.gnu.org/bugzilla/> 2012-06-20 18:24 ` aldot at gcc dot gnu.org 2012-06-20 18:31 ` bernds 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=20090707064455.16309.qmail@sourceware.org \ --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).