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 rtl-optimization/55757] Suboptimal interrupt prologue/epilogue for ARMv7-M (Cortex-M3) Date: Thu, 20 Dec 2012 16:52:00 -0000 [thread overview] Message-ID: <bug-55757-4-EXHAJFk0mZ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55757-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55757 Richard Earnshaw <rearnsha at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P3 |P5 Status|UNCONFIRMED |NEW Last reconfirmed| |2012-12-20 Ever Confirmed|0 |1 Severity|normal |enhancement --- Comment #2 from Richard Earnshaw <rearnsha at gcc dot gnu.org> 2012-12-20 16:52:05 UTC --- The code is there to re-align the stack to 64-bit alignment as required by the ABI (early versions of the M3 did not have the ability to do this in HW). The reason two registers are pushed, rather than one is that this is also needed to keep the stack aligned and pushing two registers uses less code than adjusting the stack in a separate insn. Of course, in this trivial case, the stack realignment isn't necessary as the compiler should be able to tell that nothing requires re-alignment of the stack. But it's a corner case and it's much more common for this to be needed. If you really know that you don't need stack-alignment on an M3, then just remove the interrupt attribute. It really doesn't serve any other purpose on M-profile cores other than to cause the stack realignment. Marking as an enhancement. The code generated today is correct, but sub-optimal.
next prev parent reply other threads:[~2012-12-20 16:52 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-12-20 15:04 [Bug rtl-optimization/55757] New: " freddie_chopin at op dot pl 2012-12-20 15:24 ` [Bug rtl-optimization/55757] " freddie_chopin at op dot pl 2012-12-20 16:52 ` rearnsha at gcc dot gnu.org [this message] 2012-12-20 17:08 ` freddie_chopin at op dot pl 2012-12-21 3:23 ` joey.ye at arm dot com 2012-12-21 3:32 ` joey.ye at arm dot com 2012-12-21 7:09 ` freddie_chopin at op dot pl 2013-03-02 15:23 ` web at brolinembedded dot se 2023-11-28 23:10 ` yann at poupet dot eu
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-55757-4-EXHAJFk0mZ@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).