From: Dmitry Selyutin <ghostmansd@gmail.com>
To: binutils@sourceware.org
Cc: Alan Modra <amodra@gmail.com>,
Luke Leighton <luke.leighton@gmail.com>,
Jan Beulich <jbeulich@suse.com>,
Dmitry Selyutin <ghostmansd@gmail.com>
Subject: [PATCH 0/1] ppc: support register names in macros
Date: Tue, 12 Jul 2022 16:50:56 +0300 [thread overview]
Message-ID: <20220712135057.170969-1-ghostmansd@gmail.com> (raw)
This patch is a follow-up of discussion:
https://sourceware.org/pipermail/binutils/2022-July/121719.html
Form now on, PPC assembly becomes capable of compiling such code:
.set VREG, %r0
.set REG, VREG
extsw REG, 2
extsw %r1, 1
The custom register_name() code path, as well as checks for CRs, are
deprecated; from now on, we use md_operand() routine everywhere.
Whilst we're here, let's also reuse register lookup for CFI.
Dmitry Selyutin (1):
ppc: support register names in macros
gas/config/tc-ppc.c | 206 +++++++++++++++++---------------------------
gas/config/tc-ppc.h | 9 +-
2 files changed, 86 insertions(+), 129 deletions(-)
--
2.37.0
next reply other threads:[~2022-07-12 13:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 13:50 Dmitry Selyutin [this message]
2022-07-12 13:50 ` [PATCH 1/1] " Dmitry Selyutin
2022-07-12 14:13 ` Dmitry Selyutin
2022-07-12 14:18 ` lkcl
2022-07-12 14:24 ` Dmitry Selyutin
2022-07-12 21:22 ` [PATCH v2 0/1] " Dmitry Selyutin
2022-07-12 21:22 ` [PATCH v2 1/1] " Dmitry Selyutin
2022-07-12 21:29 ` [PATCH v3 0/1] " Dmitry Selyutin
2022-07-12 21:29 ` [PATCH v3 1/1] " Dmitry Selyutin
2022-07-13 15:34 ` Alan Modra
2022-07-14 6:03 ` PowerPC: implement md_operand to parse register names Alan Modra
2022-07-14 6:04 ` [PATCH v3 1/1] ppc: support register names in macros Dmitry Selyutin
2022-07-14 6:05 ` [PATCH] ppc: use reg_name_search for CFI register lookup Dmitry Selyutin
2022-07-14 7:25 ` Alan Modra
2022-07-14 8:21 ` [PATCH v2] " Dmitry Selyutin
2022-07-14 23:01 ` Alan Modra
2022-07-14 8:23 ` [PATCH] " Dmitry Selyutin
2022-07-14 8:25 ` Dmitry Selyutin
2022-07-14 23:02 ` Alan Modra
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=20220712135057.170969-1-ghostmansd@gmail.com \
--to=ghostmansd@gmail.com \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=jbeulich@suse.com \
--cc=luke.leighton@gmail.com \
/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).