public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ramana at icerasemi dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/36409] New: Additional instructions in prologue and epilogue. Date: Sun, 01 Jun 2008 10:47:00 -0000 [thread overview] Message-ID: <bug-36409-16255@http.gcc.gnu.org/bugzilla/> (raw) Stack space creation instructions in prologue and epilogue don't get deleted. foo: sub sp, sp, #8 --> Unnecessary mov r3, #0 add sp, sp, #8 --> Unnecessary str r3, [r0] struct Foo { int *p; int *q; }; void __attribute__((noinline)) foo(struct Foo f) { *f.p = 0; } This appears to be due to get_frame_size returning the size of the incoming parameters being 8 bytes in the backend . -- Summary: Additional instructions in prologue and epilogue. Product: gcc Version: 4.3.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: rtl-optimization AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: ramana at icerasemi dot com GCC host triplet: i686-linux GCC target triplet: arm-none-eabi http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36409
next reply other threads:[~2008-06-01 10:47 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-06-01 10:47 ramana at icerasemi dot com [this message] 2009-02-04 23:39 ` [Bug target/36409] " ramana dot r at gmail dot com 2009-04-21 14:42 ` ramana at gcc dot gnu dot 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-36409-16255@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).