From: Dmitry Selyutin <ghostmansd@gmail.com>
To: binutils@sourceware.org
Cc: gdb-patches@sourceware.org, Alan Modra <amodra@gmail.com>,
Luke Kenneth Casson Leighton <lkcl@lkcl.net>
Subject: [PATCH 0/2] extend opindex and fx_pcrel_adjust to 16 bits
Date: Wed, 11 May 2022 20:59:12 +0300 [thread overview]
Message-ID: <CAMqzjetNtS0qfmNkRZcGR59GtWKFxxhZjMbS4SyieJ5dztf96A@mail.gmail.com> (raw)
With the upcoming SVP64 extension[0] to PowerPC architecture, it
became evident that PowerPC operand indices no longer fit 8 bits.
These patches extend both the operand index and the dependent
fx_pcrel_adjust field to 16 bits.
This issue has been discussed in binutils mailing list[1]; I've added
gdb-patches mailing list as well, per MAINTAINERS file instructions,
since I'm unsure if this can break the gdb interface.
You can also find these patches in perhaps a more convenient form in
the libresoc fork of binutils repository[2] (branch fx_pcrel_adjust).
[0] https://libre-soc.org
[1] https://sourceware.org/pipermail/binutils/2022-May/120775.html
[2] https://git.libre-soc.org/?p=binutils-gdb.git;a=log;h=refs/heads/fx_pcrel_adjust
Dmitry Selyutin (2):
ppc: extend opindex to 16 bits
gas/write: extend fx_pcrel_adjust to 16 bits
gas/config/tc-ppc.c | 11 ++++++-----
gas/write.h | 4 ++--
include/opcode/ppc.h | 5 ++++-
opcodes/ppc-dis.c | 12 ++++++------
4 files changed, 18 insertions(+), 14 deletions(-)
--
2.36.0
next reply other threads:[~2022-05-11 17:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 17:59 Dmitry Selyutin [this message]
2022-05-12 7:32 ` [PATCH v2 1/2] ppc: extend opindex " Dmitry Selyutin
2022-05-12 7:32 ` [PATCH v2 2/2] gas/write: extend fx_pcrel_adjust " Dmitry Selyutin
2022-05-17 11:20 ` [PATCH 0/2] extend opindex and " Dmitry Selyutin
2022-05-24 21:09 ` Dmitry Selyutin
2022-05-25 2:41 ` Alan Modra
2022-05-25 4:11 ` Dmitry Selyutin
2022-05-25 4:32 ` Alan Modra
2022-05-25 4:35 ` 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=CAMqzjetNtS0qfmNkRZcGR59GtWKFxxhZjMbS4SyieJ5dztf96A@mail.gmail.com \
--to=ghostmansd@gmail.com \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=lkcl@lkcl.net \
/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).