public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Andreas Krebbel <krebbel@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r12-3783] IBM Z: TPF: Add cc clobber to profiling expanders
Date: Wed, 22 Sep 2021 10:15:25 +0000 (GMT)	[thread overview]
Message-ID: <20210922101525.C95813858D39@sourceware.org> (raw)

https://gcc.gnu.org/g:e1223ea2f48e8588160b2948f8a1f8e47f9694fd

commit r12-3783-ge1223ea2f48e8588160b2948f8a1f8e47f9694fd
Author: Andreas Krebbel <krebbel@linux.ibm.com>
Date:   Wed Sep 22 12:13:05 2021 +0200

    IBM Z: TPF: Add cc clobber to profiling expanders
    
    The code sequence emitted uses CC internally.
    
    gcc/ChangeLog:
    
            * config/s390/tpf.md (prologue_tpf, epilogue_tpf): Add cc clobber.

Diff:
---
 gcc/config/s390/tpf.md | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/gcc/config/s390/tpf.md b/gcc/config/s390/tpf.md
index 297e9d1f755..35b37190705 100644
--- a/gcc/config/s390/tpf.md
+++ b/gcc/config/s390/tpf.md
@@ -21,7 +21,8 @@
   [(unspec_volatile [(match_operand 0 "const_int_operand" "J")
 		     (match_operand 1 "const_int_operand" "J")]
 		    UNSPECV_TPF_PROLOGUE)
-   (clobber (reg:DI 1))]
+   (clobber (reg:DI 1))
+   (clobber (reg:CC CC_REGNUM))]
   "TARGET_TPF_PROFILING"
   "larl\t%%r1,.+14\;tm\t%0,255\;bnz\t%1"
   [(set_attr "length"   "14")])
@@ -31,7 +32,8 @@
   [(unspec_volatile [(match_operand 0 "const_int_operand" "J")
 		     (match_operand 1 "const_int_operand" "J")]
 		    UNSPECV_TPF_EPILOGUE)
-   (clobber (reg:DI 1))]
+   (clobber (reg:DI 1))
+   (clobber (reg:CC CC_REGNUM))]
   "TARGET_TPF_PROFILING"
   "larl\t%%r1,.+14\;tm\t%0,255\;bnz\t%1"
   [(set_attr "length"   "14")])


                 reply	other threads:[~2021-09-22 10:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20210922101525.C95813858D39@sourceware.org \
    --to=krebbel@gcc.gnu.org \
    --cc=gcc-cvs@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).