From: Alan Modra <amodra@gmail.com>
To: Dmitry Selyutin <ghostmansd@gmail.com>
Cc: Binutils <binutils@sourceware.org>,
Luke Leighton <luke.leighton@gmail.com>,
Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH] ppc: use reg_name_search for CFI register lookup
Date: Fri, 15 Jul 2022 08:32:45 +0930 [thread overview]
Message-ID: <YtCglXnY010ZE2EL@squeak.grove.modra.org> (raw)
In-Reply-To: <CAMqzjescZ2JTsGL4UiFATmp9ehT8742+8mkEuyqVKBqoGYwy8A@mail.gmail.com>
On Thu, Jul 14, 2022 at 11:25:43AM +0300, Dmitry Selyutin wrote:
> On Thu, Jul 14, 2022 at 11:23 AM Dmitry Selyutin <ghostmansd@gmail.com> wrote:
> > Yeah sorry I totally missed that the results are tuned. Updated.
>
> Hm. Perhaps we need some test covering it? Say some as/objdump
> combination. It's a bit strange that cfi-ppc-1.d hasn't caught it.
Yes, the test isn't that good, only checking cfi for gprs.
--
Alan Modra
Australia Development Lab, IBM
prev parent reply other threads:[~2022-07-14 23:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 13:50 [PATCH 0/1] ppc: support register names in macros Dmitry Selyutin
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 [this message]
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=YtCglXnY010ZE2EL@squeak.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=ghostmansd@gmail.com \
--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).