From: "Hurugalawadi, Naveen" <Naveen.Hurugalawadi@caviumnetworks.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: [Patch, AARCH64] Remove REGISTER_PREFIX
Date: Tue, 08 Jan 2013 08:21:00 -0000 [thread overview]
Message-ID: <F3068DEED1A463459E0887A091B15493380961@BY2PRD0710MB364.namprd07.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 677 bytes --]
Hi,
AARCH64 back-end defines REGISTER_PREFIX to empty string.
Hence, it can be removed as the default value of REGISTER_PREFIX is "".
Please find attached the patch that removes REGISTER_PREFIX and all its
occurrence in aarch64 back-end. Please review the patch and let me know
if there should be any modifications?
Build and tested on aarch64-thunder-elf (using Cavium's internal
simulator).
Thanks,
Naveen.H.S
2013-01-08 Naveen H.S <Naveen.Hurugalawadi@caviumnetworks.com>
* config/aarch64/aarch64-elf.h (REGISTER_PREFIX): Remove.
* config/aarch64/aarch64.c (aarch64_print_operand): Remove all
occurrence of REGISTER_PREFIX as its empty string.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: remove_reg_pre.patch --]
[-- Type: text/x-patch; name="remove_reg_pre.patch", Size: 1803 bytes --]
--- gcc/config/aarch64/aarch64.c 2013-01-07 17:04:51.295005008 +0530
+++ gcc/config/aarch64/aarch64.c 2013-01-08 09:50:46.717051922 +0530
@@ -3348,7 +3348,7 @@ aarch64_print_operand (FILE *f, rtx x, c
output_operand_lossage ("incompatible floating point / vector register operand for '%%%c'", code);
return;
}
- asm_fprintf (f, "%s%c%d", REGISTER_PREFIX, code, REGNO (x) - V0_REGNUM);
+ asm_fprintf (f, "%c%d", code, REGNO (x) - V0_REGNUM);
break;
case 'S':
@@ -3361,8 +3361,7 @@ aarch64_print_operand (FILE *f, rtx x, c
output_operand_lossage ("incompatible floating point / vector register operand for '%%%c'", code);
return;
}
- asm_fprintf (f, "%sv%d", REGISTER_PREFIX,
- REGNO (x) - V0_REGNUM + (code - 'S'));
+ asm_fprintf (f, "v%d", REGNO (x) - V0_REGNUM + (code - 'S'));
break;
case 'w':
@@ -3371,20 +3370,19 @@ aarch64_print_operand (FILE *f, rtx x, c
64-bit). */
if (x == const0_rtx)
{
- asm_fprintf (f, "%s%czr", REGISTER_PREFIX, code);
+ asm_fprintf (f, "%czr", code);
break;
}
if (REG_P (x) && GP_REGNUM_P (REGNO (x)))
{
- asm_fprintf (f, "%s%c%d", REGISTER_PREFIX, code,
- REGNO (x) - R0_REGNUM);
+ asm_fprintf (f, "%c%d", code, REGNO (x) - R0_REGNUM);
break;
}
if (REG_P (x) && REGNO (x) == SP_REGNUM)
{
- asm_fprintf (f, "%s%ssp", REGISTER_PREFIX, code == 'w' ? "w" : "");
+ asm_fprintf (f, "%ssp", code == 'w' ? "w" : "");
break;
}
--- gcc/config/aarch64/aarch64-elf.h 2012-12-14 09:53:42.265262998 +0530
+++ gcc/config/aarch64/aarch64-elf.h 2013-01-08 09:47:17.525044826 +0530
@@ -106,7 +106,6 @@
#define ASM_COMMENT_START "//"
-#define REGISTER_PREFIX ""
#define LOCAL_LABEL_PREFIX "."
#define USER_LABEL_PREFIX ""
next reply other threads:[~2013-01-08 8:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 8:21 Hurugalawadi, Naveen [this message]
2013-01-23 9:48 ` Marcus Shawcroft
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=F3068DEED1A463459E0887A091B15493380961@BY2PRD0710MB364.namprd07.prod.outlook.com \
--to=naveen.hurugalawadi@caviumnetworks.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).