public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Kewen Lin <linkw@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-283] rs6000: Fix constraint v with rs6000_constraints[RS6000_CONSTRAINT_v]
Date: Wed, 11 May 2022 07:22:44 +0000 (GMT)	[thread overview]
Message-ID: <20220511072244.217DA3850435@sourceware.org> (raw)

https://gcc.gnu.org/g:55aa130ef112c6f2c8ef85c218455464c6b29d60

commit r13-283-g55aa130ef112c6f2c8ef85c218455464c6b29d60
Author: Kewen Lin <linkw@linux.ibm.com>
Date:   Wed May 11 01:18:30 2022 -0500

    rs6000: Fix constraint v with rs6000_constraints[RS6000_CONSTRAINT_v]
    
    Currently we hardcode ALTIVEC_REGS for register constraint v and
    RS6000_CONSTRAINT_v looks confusing, this is to fix it with
    rs6000_constraints[RS6000_CONSTRAINT_v] to align with some other
    existing register constraints with RS6000_CONSTRAINT_*.
    
    gcc/ChangeLog:
    
            * config/rs6000/constraints.md (register constraint v): Use
            rs6000_constraints[RS6000_CONSTRAINT_v] instead of ALTIVEC_REGS.

Diff:
---
 gcc/config/rs6000/constraints.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/config/rs6000/constraints.md b/gcc/config/rs6000/constraints.md
index 7aaffd9f9a8..b361893e289 100644
--- a/gcc/config/rs6000/constraints.md
+++ b/gcc/config/rs6000/constraints.md
@@ -37,7 +37,7 @@
    historically @code{f} was for single-precision and @code{d} was for
    double-precision floating point.")
 
-(define_register_constraint "v" "ALTIVEC_REGS"
+(define_register_constraint "v" "rs6000_constraints[RS6000_CONSTRAINT_v]"
   "An Altivec vector register (VR), @code{v0}@dots{}@code{v31}.")
 
 (define_register_constraint "wa" "rs6000_constraints[RS6000_CONSTRAINT_wa]"


                 reply	other threads:[~2022-05-11  7:22 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=20220511072244.217DA3850435@sourceware.org \
    --to=linkw@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).