public inbox for binutils-cvs@sourceware.org
 help / color / mirror / Atom feed
From: liu & zhensong <liuzhensong@sourceware.org>
To: bfd-cvs@sourceware.org
Subject: [binutils-gdb] binutils: NEWS: Announce LoongArch changes in the 2.41 cycle
Date: Mon,  3 Jul 2023 01:04:06 +0000 (GMT)	[thread overview]
Message-ID: <20230703010406.24D1838582BD@sourceware.org> (raw)

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

commit 0ed3ac2f4a06cb842065d4cf2d1fe1c269d508b9
Author: WANG Xuerui <git@xen0n.name>
Date:   Sun Jul 2 19:10:52 2023 +0800

    binutils: NEWS: Announce LoongArch changes in the 2.41 cycle
    
    binutils/ChangeLog:
    
            * NEWS: Mention LoongArch changes for 2.41.
    
    Signed-off-by: WANG Xuerui <git@xen0n.name>

Diff:
---
 binutils/NEWS | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/binutils/NEWS b/binutils/NEWS
index 834e648db6c..939cfead8de 100644
--- a/binutils/NEWS
+++ b/binutils/NEWS
@@ -29,6 +29,20 @@
 * The RISC-V port now supports the following vendor-defined extensions:
   - XVentanaCondOps
 
+* The LoongArch port now supports the following extensions:
+  - LSX (Loongson SIMD eXtension; 128-bit vectors)
+  - LASX (Loongson Advanced SIMD eXtension; 256-bit vectors)
+  - LVZ (Loongson Virtualization extension)
+  - LBT (Loongson Binary Translation extension)
+
+* The LoongArch disassembly output received the following tweaks:
+  - Colored output is now supported.
+  - Some pseudo-instructions are now shown in place of the canonical forms,
+    where semantics are equivalent. A disassembler option '-M no-aliases' is
+    added to disable the new behavior.
+  - Signed immediates are no longer printed with their hex representation.
+  - Unrecognized instruction words are now shown with '.word'.
+
 Changes in 2.40:
 
 * Objdump has a new command line option --show-all-symbols which will make it

                 reply	other threads:[~2023-07-03  1:04 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=20230703010406.24D1838582BD@sourceware.org \
    --to=liuzhensong@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).