This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: altivec: fix register names
- To: David Edelsohn <dje at watson dot ibm dot com>
- Subject: Re: altivec: fix register names
- From: Aldy Hernandez <aldyh at redhat dot com>
- Date: 09 Nov 2001 19:09:03 -0500
- Cc: gcc patches <gcc-patches at gcc dot gnu dot org>
- References: <200111092358.SAA26122@makai.watson.ibm.com>
> Why can't the default register name be an undecorated number
> instead of prepending "v" or "%v"? I know its not pretty, but it is the
> shortest and consistent with the GPRs and FPRs. Use -mregnames if you
> want it to look pretty.
i just didn't want to overlap the GPRs by just having 0, 1, etc... but i
guess since cr0, cr1, etc is doing the same, it won't hurt.
is this better?
--
Aldy Hernandez E-mail: aldyh@redhat.com
Professional Gypsy
Red Hat, Inc.
2001-11-09 Aldy Hernandez <aldyh@redhat.com>
* config/rs6000/rs6000.c (rs6000_reg_names): Remove leading "v" or
altivec registers.
Index: config/rs6000/rs6000.c
===================================================================
RCS file: /cvs/uberbaum/gcc/config/rs6000/rs6000.c,v
retrieving revision 1.231
diff -c -p -r1.231 rs6000.c
*** rs6000.c 2001/11/09 07:14:16 1.231
--- rs6000.c 2001/11/10 00:05:00
*************** char rs6000_reg_names[][8] =
*** 173,182 ****
"0", "1", "2", "3", "4", "5", "6", "7",
"xer",
/* AltiVec registers. */
! "v0", "v1", "v2", "v3", "v4", "v5", "v6", "v7",
! "v8", "v9", "v10", "v11", "v12", "v13", "v14", "v15",
! "v16", "v17", "v18", "v19", "v20", "v21", "v22", "v23",
! "v24", "v25", "v26", "v27", "v28", "v29", "v30", "v31",
"vrsave"
};
--- 173,182 ----
"0", "1", "2", "3", "4", "5", "6", "7",
"xer",
/* AltiVec registers. */
! "0", "1", "2", "3", "4", "5", "6", "7",
! "8", "9", "10", "11", "12", "13", "14", "15",
! "16", "17", "18", "19", "20", "21", "22", "23",
! "24", "25", "26", "27", "28", "29", "30", "31",
"vrsave"
};