public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Michael Eager <eager@eagercon.com>
To: Neal Frager <neal.frager@amd.com>, binutils@sourceware.org
Cc: ibai.erkiaga-elorza@amd.com, nagaraju.mekala@amd.com,
	mark.hatle@amd.com, sadanand.mutyala@amd.com,
	appa.rao.nali@amd.com, vidhumouli.hunsigida@amd.com,
	luca.ceresoli@bootlin.com, nickc@redhat.com, mark@klomp.org,
	eager@eagercon.com, macro@orcam.me.uk
Subject: Re: [PATCH v6 1/2] opcodes: microblaze: Add new bit-field instructions
Date: Sun, 15 Oct 2023 09:30:35 -0700	[thread overview]
Message-ID: <db0d4d50-7803-f678-7987-c2f5269b917f@eagercon.com> (raw)
In-Reply-To: <20231013072856.638728-1-neal.frager@amd.com>

Neal --

When I run the test suite I see many segfaults.

Take a look at
gas/config/tc-microblaze.c +418:
md_begin() ...
   /* Insert unique names into hash table.  */
   for (opcode = microblaze_opcodes; opcode->name; opcode ++)
     str_hash_insert (opcode_hash_control, opcode->name, opcode, 0);

compare the end of the microblaze_opcodes table:
binutils/opcodes/microblaze-opc.h +427
microblaze_opcodes[] ...
   {"", 0, 0, 0, 0, 0, 0, 0, 0},

It looks like there is a mismatch on termination condition.

I changed this to
   {NULL, 0, 0, 0, 0, 0, 0, 0, 0},

I'm at a loss to explain why this did not fail earlier.

On 10/13/23 00:28, Neal Frager wrote:
> This patches adds new bsefi and bsifi instructions.
> BSEFI- The instruction shall extract a bit field from a
> register and place it right-adjusted in the destination register.
> The other bits in the destination register shall be set to zero.
> BSIFI- The instruction shall insert a right-adjusted bit field
> from a register at another position in the destination register.
> The rest of the bits in the destination register shall be unchanged.

...

> diff --git a/opcodes/microblaze-dis.c b/opcodes/microblaze-dis.c
> index 12981abfea1..b2d3f19337c 100644
> --- a/opcodes/microblaze-dis.c
> +++ b/opcodes/microblaze-dis.c
> @@ -427,6 +442,14 @@ print_insn_microblaze (bfd_vma memaddr, struct disassemble_info * info)
>   	  /* For mbar 16 or sleep insn.  */
>   	case INST_TYPE_NONE:
>   	  break;
> +	  /* For bit field insns.  */
> +	case INST_TYPE_RD_R1_IMMW_IMMS:
> +	  print_func (stream, "\t%s, %s, %s, %s",
> +			get_field_rd (&buf, inst),
> +			get_field_r1 (&buf, inst),
> +			get_field_immw (&buf, inst),
> +			get_field_imm5 (&buf, inst));
> +	  break;

Fixed indent.

Trimmed commit message.

Committed.

-- 
Michael Eager


  parent reply	other threads:[~2023-10-15 16:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-13  7:28 Neal Frager
2023-10-13  7:28 ` [PATCH v6 2/2] gas: testsuite: microblaze: Add new bit-field tests Neal Frager
2023-10-17 22:58   ` Michael Eager
2023-10-15 16:30 ` Michael Eager [this message]
2023-10-15 16:48   ` [PATCH v6 1/2] opcodes: microblaze: Add new bit-field instructions Frager, Neal
2023-10-19  3:40     ` Alan Modra
2023-10-19  3:53       ` Alan Modra
2023-10-19  6:40         ` Frager, Neal
2023-10-19 10:23           ` Alan Modra
2023-10-19 13:20         ` Frager, Neal
2023-10-19 21:30           ` Alan Modra
2023-10-20  6:28             ` Frager, Neal

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=db0d4d50-7803-f678-7987-c2f5269b917f@eagercon.com \
    --to=eager@eagercon.com \
    --cc=appa.rao.nali@amd.com \
    --cc=binutils@sourceware.org \
    --cc=ibai.erkiaga-elorza@amd.com \
    --cc=luca.ceresoli@bootlin.com \
    --cc=macro@orcam.me.uk \
    --cc=mark.hatle@amd.com \
    --cc=mark@klomp.org \
    --cc=nagaraju.mekala@amd.com \
    --cc=neal.frager@amd.com \
    --cc=nickc@redhat.com \
    --cc=sadanand.mutyala@amd.com \
    --cc=vidhumouli.hunsigida@amd.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).