public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "daniel dot sherwood at sepura dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/38571] GCC/THUMB generates unnecessary padding between functions Date: Thu, 18 Dec 2008 17:44:00 -0000 [thread overview] Message-ID: <20081218174329.25381.qmail@sourceware.org> (raw) In-Reply-To: <bug-38571-17095@http.gcc.gnu.org/bugzilla/> ------- Comment #5 from daniel dot sherwood at sepura dot com 2008-12-18 17:43 ------- Following comment received from Richard.Earnshaw@arm.com by e-mail. ====== Often this is necessary (for example, if the function contains a literal pool); but it isn't always so. Again, if there is no existing case in bugzilla, perhaps you could file one. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38571
next prev parent reply other threads:[~2008-12-18 17:44 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-12-18 17:42 [Bug c/38571] New: " daniel dot sherwood at sepura dot com 2008-12-18 17:43 ` [Bug c/38571] " daniel dot sherwood at sepura dot com 2008-12-18 17:43 ` daniel dot sherwood at sepura dot com 2008-12-18 17:43 ` daniel dot sherwood at sepura dot com 2008-12-18 17:43 ` daniel dot sherwood at sepura dot com 2008-12-18 17:44 ` daniel dot sherwood at sepura dot com [this message] 2009-04-22 23:09 ` [Bug target/38571] [arm] -mthumb " ramana at gcc dot gnu dot org 2009-04-23 0:46 ` pinskia at gcc dot gnu dot org 2009-04-24 16:01 ` ramana at gcc dot gnu dot org 2009-04-30 10:05 ` ramana at gcc dot gnu dot org 2009-04-30 10:05 ` ramana at gcc dot gnu dot org 2009-04-30 10:06 ` 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=20081218174329.25381.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).