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 target/53735] thumb1 spill failure with -Os Date: Mon, 05 Aug 2013 21:34:00 -0000 [thread overview] Message-ID: <bug-53735-4-qOKxRHtHgs@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53735-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53735 Richard Earnshaw <rearnsha at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #5 from Richard Earnshaw <rearnsha at gcc dot gnu.org> --- Realistically, we're never going to be able to fix this. You've tied the compilers hands behind it's back and it's then unable to keep its balance when you give it a push. In Thumb1 code, when optimizing for space, you've got just r0-r6 available in general (r7 is used for the frame pointer). Your source code tries to use all 7 of them (a1[r0]-a4[r3], v1[r4], r5 and v3[r6]). That just leaves r7 (the frame pointer) for the compiler to use for everything, so it's no surprise that things then fall apart.
prev parent reply other threads:[~2013-08-05 21:34 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-06-20 18:56 [Bug target/53735] New: " aldot at gcc dot gnu.org 2012-06-20 18:58 ` [Bug target/53735] " aldot at gcc dot gnu.org 2012-07-17 9:34 ` ramana at gcc dot gnu.org 2012-07-24 9:04 ` zhuolin.liu at arm dot com 2012-07-26 7:51 ` zhenqiang.chen at linaro dot org 2013-08-05 21:34 ` rearnsha at gcc dot gnu.org [this message]
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-53735-4-qOKxRHtHgs@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).