public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/63718] [5 Regression] ARM Thumb1 bootstrap fail after fuse-caller-save info in cprop-hardreg
Date: Mon, 03 Nov 2014 10:17:00 -0000	[thread overview]
Message-ID: <bug-63718-4-Z6BjXxZzap@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63718-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63718

vries at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |vries at gcc dot gnu.org

--- Comment #5 from vries at gcc dot gnu.org ---
Created attachment 33874
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33874&action=edit
tentative patch, adds missing clobbers

Joey,

thanks for doing the analysis and the clear bug report. I cannot formally
confirm at this point since I don't have an arm bootstrap setup, but I agree,
those missing clobbers (while not causing problems otherwise) will cause
problems with fuse-caller-save.

I'd say the fix is to add the missing clobbers. Attached tentative patch
implements that fix.

Using the patch, I build a c-only arm compiler, compiled an example with
-mthumb and -march=armv4t and observed the new clobbers on the return in the
final dump:
...
(jump_insn 19 18 20 (parallel [
            (unspec_volatile [
                    (return)
            ] VUNSPEC_EPILOGUE)
            (clobber (reg:SI 0 r0))
            (clobber (reg:SI 1 r1))
            (clobber (reg:SI 2 r2))
            (clobber (reg:SI 3 r3))
        ]) test.c:9 773 {*epilogue_insns}
     (expr_list:REG_UNUSED (reg:SI 3 r3)
        (expr_list:REG_UNUSED (reg:SI 2 r2)
            (expr_list:REG_UNUSED (reg:SI 1 r1)
                (nil))))
 -> return)
...

Could you try out the patch and see if it fixes things for you?

Thanks,
- Tom


  parent reply	other threads:[~2014-11-03 10:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-03  7:32 [Bug rtl-optimization/63718] New: " joey.ye at arm dot com
2014-11-03  8:15 ` [Bug rtl-optimization/63718] " joey.ye at arm dot com
2014-11-03  8:16 ` joey.ye at arm dot com
2014-11-03  8:38 ` joey.ye at arm dot com
2014-11-03  9:19 ` [Bug rtl-optimization/63718] [5 Regression] " rguenth at gcc dot gnu.org
2014-11-03 10:17 ` vries at gcc dot gnu.org [this message]
2014-11-03 10:26 ` joey.ye at arm dot com
2014-11-04  1:46 ` joey.ye at arm dot com
2014-11-10  1:57 ` joey.ye at arm dot com
2014-11-10  7:50 ` vries at gcc dot gnu.org
2014-11-18 15:08 ` vries at gcc dot gnu.org
2014-11-18 15:09 ` vries at gcc dot gnu.org
2014-11-19 17:44 ` vries at gcc dot gnu.org
2014-11-20  2:34 ` joey.ye at arm dot com
2014-11-20 12:46 ` rguenth at gcc dot gnu.org
2014-11-24 17:06 ` vries at gcc dot gnu.org
2014-12-02 14:13 ` joey.ye at arm dot com
2014-12-02 17:18 ` vries 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=bug-63718-4-Z6BjXxZzap@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: link
Be 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).