public inbox for binutils-cvs@sourceware.org
 help / color / mirror / Atom feed
From: Andreas Krebbel <krebbel@sourceware.org>
To: bfd-cvs@sourceware.org
Subject: [binutils-gdb] s390: Correct prno instruction name
Date: Thu, 23 Nov 2023 14:53:35 +0000 (GMT)	[thread overview]
Message-ID: <20231123145335.6483D385C41D@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=6e1d1b2e7b2e12e53fa287387fbbca9c56dc29d0

commit 6e1d1b2e7b2e12e53fa287387fbbca9c56dc29d0
Author: Jens Remus <jremus@linux.ibm.com>
Date:   Thu Nov 23 15:48:59 2023 +0100

    s390: Correct prno instruction name
    
    IBM z13 (arch11) introduced ppno (Perform Pseudorandom Number Operation).
    IBM z14 (arch12) introduced prno (Perform Random Number Operation) and
    deprecated ppno.
    
    opcodes/
            * s390-opc.txt: Correct prno instruction name.
    
    Signed-off-by: Jens Remus <jremus@linux.ibm.com>
    Reviewed-by: Andreas Krebbel <krebbel@linux.ibm.com>

Diff:
---
 opcodes/s390-opc.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/opcodes/s390-opc.txt b/opcodes/s390-opc.txt
index 674c0cf1987..853758b96aa 100644
--- a/opcodes/s390-opc.txt
+++ b/opcodes/s390-opc.txt
@@ -1910,7 +1910,7 @@ e30000000049 stgsc RXY_RRRD "store guarded storage controls" arch12 zarch
 
 b929 kma RRF_R0RR "cipher message with galois counter mode" arch12 zarch
 
-b93c prno RRE_RR "perform pseudorandom number operation" arch12 zarch
+b93c prno RRE_RR "perform random number operation" arch12 zarch
 b9a1 tpei RRE_RR "test pending external interruption" arch12 zarch
 b9ac irbm RRE_RR "insert reference bits multiple" arch12 zarch

                 reply	other threads:[~2023-11-23 14:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20231123145335.6483D385C41D@sourceware.org \
    --to=krebbel@sourceware.org \
    --cc=bfd-cvs@sourceware.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).