public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Sa Liu <SALIU@de.ibm.com>
To: gcc-patches@gcc.gnu.org
Subject: [PATCH] Handel REG_LIBCALL note after split
Date: Thu, 09 Aug 2007 13:40:00 -0000	[thread overview]
Message-ID: <OFDBB8991B.357E74CF-ONC1257330.0040277E-C1257332.004B48F3@de.ibm.com> (raw)

This patch relink the insns with REG_LIBCALL note and with REG_RETVAL note 
after split.
The discussion in GCC mailing list can be found here:
http://gcc.gnu.org/ml/gcc/2007-07/msg00925.html

The patch has been tested on spu with gcc test suits and got no 
regression.

Is it now OK for the mainline?

Thanks,
Sa

Index: gcc/emit-rtl.c
===================================================================
--- gcc.orig/emit-rtl.c
+++ gcc/emit-rtl.c
@@ -3129,7 +3129,7 @@ try_split (rtx pat, rtx trial, int last)
   rtx before = PREV_INSN (trial);
   rtx after = NEXT_INSN (trial);
   int has_barrier = 0;
-  rtx tem;
+  rtx tem, note_retval;
   rtx note, seq;
   int probability;
   rtx insn_last, insn;
@@ -3264,6 +3264,16 @@ try_split (rtx pat, rtx trial, int last)
            }
          break;
 #endif
+       case REG_LIBCALL:
+       /* Relink the insns with REG_LIBCALL note and with REG_RETVAL note 

+          after split.  */
+           REG_NOTES (insn_last) 
+               = gen_rtx_EXPR_LIST (REG_LIBCALL,
+                                    XEXP (note, 0),
+                                    REG_NOTES (insn_last)); 
+           note_retval = find_reg_note (XEXP (note, 0), REG_RETVAL, 
NULL);
+           XEXP (note_retval, 0) = insn_last;
+         break;
 
        default:
          break;




             reply	other threads:[~2007-08-09 13:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-09 13:40 Sa Liu [this message]
2007-08-10 15:09 ` Ian Lance Taylor
2007-08-15 12:16 ` Jakub Jelinek

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=OFDBB8991B.357E74CF-ONC1257330.0040277E-C1257332.004B48F3@de.ibm.com \
    --to=saliu@de.ibm.com \
    --cc=gcc-patches@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).