public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Jens Remus <jremus@linux.ibm.com>
To: Nick Clifton <nickc@redhat.com>, binutils@sourceware.org
Cc: Andreas Krebbel <krebbel@linux.ibm.com>
Subject: Re: [PATCH 0/6] s390: Add missing extended mnemonics
Date: Wed, 22 Nov 2023 17:25:22 +0100	[thread overview]
Message-ID: <4b43a052-377e-4476-bca3-1eeead156755@linux.ibm.com> (raw)
In-Reply-To: <df09675d-3267-415b-8a29-cdc9029c884e@redhat.com>

Hello Nick,

Am 22.11.2023 um 13:13 schrieb Nick Clifton:
>> This patch series adds the following extended mnemonics (grouped by
>> function) to the s390 target architecture:
>> - jc, jcth
>> - lfi, llgfi, llghi
>> - notr, notgr
>> - risbhgz, risblgz
>> - rnsbgt, rosbgt, rxsbgt

...

>> Patches 1-3 are preparatory changes. Patch 4 aligns the optional operand
>> definition. Patch 5 adds the missing extended mnemonics. Patch 6 corrects
>> an instruction name.

...

> Patch series approved - please apply.

Thanks! Andreas will take care.

> Do these new instructions have a name to cover them as a whole ?
> I am thinking that it would be nice to have an entry in the gas/NEWS
> file that says something like "add support for the XXX extension to the
> s390x architecture".

No, these extended mnemonics were simply missed to be added over time. I 
did a cross check against the latest version of the IBM z/Architecture 
Principles of Operation specification to identify them.

Extended mnemonics are purely syntactic sugar and actually assemble into 
a base mnemonic. The identical instruction could be coded by using the 
existing base mnemonic instead of the new extended mnemonic. The 
disassembler for s390 tries to disassemble into the extended mnemonic, 
if it is not a simple alias, which makes the disassembly more human 
readable.

> One other, minor thing.  I tried to look at the documentation that
> you referenced in patch 5:
> 
>  > Add extended mnemonics specified in the z/Architecture Principles of
>  > Operation [1] and z/Architecture Reference Summary [2], that were
>  > previously missing from the opcode table.
> 
>  > [1] IBM z/Architecture Principles of Operation, SA22-7832-13,
>  >    https://www.ibm.com/support/pages/zarchitecture-principles-operation
>  > [2] IBM z/Architecture Reference Summary, SA22-7871-11,
>  >    https://www.ibm.com/support/pages/zarchitecture-reference-summary
> 
> I found that link [2] diverts to a "500: Internal Server Error" page
> and link [1] would not let me download the document without first
> registering for an IBMid, which I can do, but it is not really Open
> Source friendly...

Thanks for the hint! I have sent a V2 of my patches 3 and 4 with direct 
links to the documentation. These should work without an IBMid.

Regards,
Jens
-- 
Jens Remus
Linux on Z Development (D3303) and z/VSE Support
+49-(0)7031-16-1128 Office
JREMUS@de.ibm.com

IBM

IBM Deutschland Research & Development GmbH; Vorsitzender des 
Aufsichtsrats: Gregor Pillen; Geschäftsführung: David Faller; Sitz der 
Gesellschaft: Böblingen; Registergericht: Amtsgericht Stuttgart, HRB 243294
IBM Data Privacy Statement: https://www.ibm.com/privacy/

  reply	other threads:[~2023-11-22 16:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-20 14:06 Jens Remus
2023-11-20 14:06 ` [PATCH 1/6] s390: Position independent verification of relative addressing Jens Remus
2023-11-20 14:06 ` [PATCH 2/6] s390: Add brasl edge test cases from ESA to z/Architecture Jens Remus
2023-11-20 14:06 ` [PATCH 3/6] s390: Make operand table indices relative to each other Jens Remus
2023-11-20 14:06 ` [PATCH 4/6] s390: Align optional operand definition to specs Jens Remus
2023-11-22 16:06   ` [PATCH v2 " Jens Remus
2023-11-23 11:58     ` Nick Clifton
2023-11-20 14:06 ` [PATCH 5/6] s390: Add missing extended mnemonics Jens Remus
2023-11-22 16:07   ` [PATCH v2 " Jens Remus
2023-11-23 11:59     ` Nick Clifton
2023-11-20 14:06 ` [PATCH 6/6] s390: Correct prno instruction name Jens Remus
2023-11-22 12:13 ` [PATCH 0/6] s390: Add missing extended mnemonics Nick Clifton
2023-11-22 16:25   ` Jens Remus [this message]
2023-11-23 14:53     ` Andreas Krebbel

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=4b43a052-377e-4476-bca3-1eeead156755@linux.ibm.com \
    --to=jremus@linux.ibm.com \
    --cc=binutils@sourceware.org \
    --cc=krebbel@linux.ibm.com \
    --cc=nickc@redhat.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).