public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Alan Modra <amodra@gmail.com>
To: Dmitry Selyutin <ghostmansd@gmail.com>
Cc: binutils@sourceware.org, Luke Kenneth Casson Leighton <lkcl@lkcl.net>
Subject: Re: PPC binutils opcodes
Date: Wed, 11 May 2022 22:43:27 +0930	[thread overview]
Message-ID: <Ynu2d9TZfS1B8k1L@squeak.grove.modra.org> (raw)
In-Reply-To: <CAMqzjesn5FWA+D9C2Fet_vNAj4YnHvhMaxopeFuAeh2kG=ZRXQ@mail.gmail.com>

On Wed, May 11, 2022 at 12:24:21PM +0300, Dmitry Selyutin wrote:
> Hello folks,
> 
> long time no news. We're still extending PowerPC with SVP64
> extensions[0], and, as part of this large task, we're updating
> binutils respectively[1].
> With the recent commit[2], I've hit the limit on count of operands
> stored in powerpc_operands array, and now I'm somewhat unsure of how
> to address it.

Yes, we are getting close to the limit on mainline, 241 entries.

> The trivial and obvious solution to increase the size of the operand
> index[3] can be done, but it appears there is another obstacle this
> time[4].
> 
> Considering fx_pcrel_adjust field, it appears to be shared and it has
> exactly 8 bits[5]. This is enforced by the assertion above, but also
> by other places[6].

Increasing the size of fx_pcrel_adjust should be fine, adjusting the
assertion and removing the silly mask to 8 bits.  Another option
is to add a field to tc-ppc.h:_ppc_fix_extra and use that instead of
fx_pcrel_adjust in tc-ppc.c.

-- 
Alan Modra
Australia Development Lab, IBM

  parent reply	other threads:[~2022-05-11 13:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-11  9:24 Dmitry Selyutin
2022-05-11 10:09 ` Luke Kenneth Casson Leighton
2022-05-11 13:13 ` Alan Modra [this message]
2022-05-11 16:39   ` Dmitry Selyutin
2022-05-11 19:46   ` Luke Kenneth Casson Leighton
2022-05-11 20:06     ` Dmitry Selyutin
2022-05-12  6:32       ` lkcl
2022-05-15 17:38         ` Luke Kenneth Casson Leighton
2022-05-11 23:38     ` Alan Modra
2022-05-18  3:20       ` Peter Bergner
2022-05-18  9:57         ` Luke Kenneth Casson Leighton

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=Ynu2d9TZfS1B8k1L@squeak.grove.modra.org \
    --to=amodra@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=ghostmansd@gmail.com \
    --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).