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>,
Andreas Schwab <schwab@linux-m68k.org>
Subject: Re: [PATCH 0/2] extend opindex and fx_pcrel_adjust to 16 bits
Date: Tue, 17 May 2022 14:20:37 +0300 [thread overview]
Message-ID: <CAMqzjetPdsU6egTzyWh+_EX7V81ku_ad7=qUPi5qjjzPB3gPdA@mail.gmail.com> (raw)
In-Reply-To: <CAMqzjetNtS0qfmNkRZcGR59GtWKFxxhZjMbS4SyieJ5dztf96A@mail.gmail.com>
On Wed, May 11, 2022 at 8:59 PM Dmitry Selyutin <ghostmansd@gmail.com> wrote:
> With the upcoming SVP64 extension[0] to PowerPC architecture, it
> became evident that PowerPC operand indices no longer fit 8 bits.
Hello all, this is a kind reminder on v2 patches. Thank you for your
suggestions and remarks on the first revision.
The new revision has been submitted correctly, as part of a thread[0][1][2].
Do you have more comments or suggestions on these patches? Can these
be submitted?
[0] https://sourceware.org/pipermail/binutils/2022-May/120783.html
[1] https://sourceware.org/pipermail/binutils/2022-May/120804.html
[2] https://sourceware.org/pipermail/binutils/2022-May/120803.html
next prev parent reply other threads:[~2022-05-17 11:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 17:59 Dmitry Selyutin
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 ` Dmitry Selyutin [this message]
2022-05-24 21:09 ` [PATCH 0/2] extend opindex and " 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='CAMqzjetPdsU6egTzyWh+_EX7V81ku_ad7=qUPi5qjjzPB3gPdA@mail.gmail.com' \
--to=ghostmansd@gmail.com \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=lkcl@lkcl.net \
--cc=schwab@linux-m68k.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).