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/66444] [5/6 Regression] Miscompilation of Xen since r211078
Date: Sun, 07 Jun 2015 22:03:00 -0000	[thread overview]
Message-ID: <bug-66444-4-L8rR2hmpzQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66444-4@http.gcc.gnu.org/bugzilla/>

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

vries at gcc dot gnu.org changed:

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

--- Comment #1 from vries at gcc dot gnu.org ---
Tentative patch:
...
diff --git a/gcc/postreload.c b/gcc/postreload.c
index 7ecca15..1cc7b14 100644
--- a/gcc/postreload.c
+++ b/gcc/postreload.c
@@ -1352,9 +1352,12 @@ reload_combine (void)
       if (CALL_P (insn))
        {
          rtx link;
+         HARD_REG_SET used_regs;
+
+         get_call_reg_set_usage (insn, &used_regs, call_used_reg_set);

          for (r = 0; r < FIRST_PSEUDO_REGISTER; r++)
-           if (call_used_regs[r])
+           if (TEST_HARD_REG_BIT (used_regs, r))
              {
                reg_state[r].use_index = RELOAD_COMBINE_MAX_USES;
                reg_state[r].store_ruid = reload_combine_ruid;
...

Output with patch:
...
        movabsq $962072674304, %r8
        salq    $5, %rax
        addq    %rax, %r8
        movq    %r8, %rdi
        call    fn1
        movq    %r8, %rdi
        call    fn2
...


  parent reply	other threads:[~2015-06-07 22:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-06 19:39 [Bug rtl-optimization/66444] New: " jakub at gcc dot gnu.org
2015-06-06 19:40 ` [Bug rtl-optimization/66444] " jakub at gcc dot gnu.org
2015-06-07 22:03 ` vries at gcc dot gnu.org [this message]
2015-06-07 22:09 ` vries at gcc dot gnu.org
2015-06-08  6:42 ` jakub at gcc dot gnu.org
2015-06-08  8:31 ` vries at gcc dot gnu.org
2015-06-08  8:34 ` vries at gcc dot gnu.org
2015-06-08  8:36 ` jakub at gcc dot gnu.org
2015-06-08  9:41 ` vries at gcc dot gnu.org
2015-06-08  9:44 ` jakub at gcc dot gnu.org
2015-06-08 12:05 ` vries at gcc dot gnu.org
2015-06-08 17:00 ` vries at gcc dot gnu.org
2015-06-08 17:09 ` vries at gcc dot gnu.org
2015-06-08 17:11 ` vries at gcc dot gnu.org
2015-06-08 17:25 ` 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-66444-4-L8rR2hmpzQ@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).