From: Xi Ruoyao <xry111@xry111.site>
To: Nick Clifton <nickc@redhat.com>,
binutils@sourceware.org, info-gnu@gnu.org, dje.gcc@gmail.com
Subject: Re: GNU Binutils 2.40 released
Date: Sun, 15 Jan 2023 17:17:52 +0800 [thread overview]
Message-ID: <0155d76115eabcc4a85f1d855b2bbd1547793e73.camel@xry111.site> (raw)
In-Reply-To: <87h6wtgmhy.fsf@redhat.com>
Hi Nick,
binutils-2.40.tar.xz is available at sourceware.org, but not
ftp.gnu.org. I guess something is wrong?
On Sat, 2023-01-14 at 15:32 +0000, Nick Clifton via Binutils wrote:
> Hi Everyone,
>
> We are pleased to announce that version 2.40 of the GNU Binutils
> project
> sources have been released and are now available for download at:
>
> https://ftp.gnu.org/gnu/binutils
> https://sourceware.org/pub/binutils/releases/
>
> SHA256 checksums:
> f8298eb153a4b37d112e945aa5cb2850040bcf26a3ea65b5a715c83afe05e48a binutils-2.40.tar.bz2
> f8abdb11141faf0cec3cba64ff9d07158a9b6bc45b48f5236501f7d64edcb781 binutils-2.40.tar.bz2.sig
> d7f82c4047decf43a6f769ac32456a92ddb6932409a585c633cdd4e9df23d956 binutils-2.40.tar.gz
> b173f69e23aa1917dfbc6f5668c058676ffba02d69ab5e2f5592a9dc2897bfcf binutils-2.40.tar.gz.sig
> 48e65ecee1bbcf334d7efb4ea8487fe048dea522e5da3bdf7fa42b1ec779ea33 binutils-2.40.tar.lz
> 04d16bf51043bedd9de98398ef8672a8a496e0351a628fb77e0b39146a13635f binutils-2.40.tar.lz.sig
> 0f8a4c272d7f17f369ded10a4aca28b8e304828e95526da482b0ccc4dfc9d8e1 binutils-2.40.tar.xz
> a5d04157464dda2f3a616db980553a1e4fafe350c0e01e3de9abdc161ece690b binutils-2.40.tar.xz.sig
>
> As an experiment these tarballs were made with the new "-r <date>"
> option supported by the src-release.sh script. This attempts to
> make
> reproducible tarballs by sorting the files and passing the
> "--mtime=<date>" option to tar. The date used for these tarballs
> was
> obtained by running:
>
> git log -1 --format=%cd --date=format:%F bfd/version.m4
>
> This release contains numerous bug fixes, and also the following new
> features:
>
> * Support for more Intel, ARM, Risc-V architecture extensions.
>
> * Support for generating and reading compressed debug sections
> using the zstd compression format.
>
> * Support for the SFRAME unwind format.
>
> * Support for the CTF debug format.
>
> * The objdump tool now has an option to enhance its disassembly
> output by showing all of the symbols that match an address,
> instead of just the first symbol.
>
> * The objdump tool's disassembler is now also able to use colors
> to
> distinguish differents parts of each instruction. This feature
> is only supported by a limited set of architectures at the
> moment.
>
> * The linker (ld) has a new command line option to disable the
> generation of warning and error messages. This can be useful
> when it is known that the link will not be successful, but
> there
> is still a need to create a binary.
>
> For more information see:
>
>
> https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob_plain;f=gas/NEWS;;hb=refs/tags/binutils-2_40
>
> https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob_plain;f=ld/NEWS;hb=refs/tags/binutils-2_40
>
> https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob_plain;f=binutils/NEWS;hb=refs/tags/binutils-2_40
>
> In addition there is now a GNU Binutils wiki site, which attempts to
> answer some of the more social needs of the GNU Binutils project.
> This is still a work in progress however, and its contents, format
> and
> location may change in the future:
>
> https://sourceware.org/binutils/wiki/HomePage
>
> Our thanks go out to all of the binutils contributors, past and
> present, for helping to make this release possible.
>
> Cheers
> Nick Clifton
> GNU Binutils co-chief maintainer
>
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2023-01-15 9:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-14 15:32 Nick Clifton
2023-01-15 9:17 ` Xi Ruoyao [this message]
2023-01-16 10:58 ` Nick Clifton
2023-01-16 11:35 ` Nick Clifton
2023-01-15 21:18 ` Achim Gratz
2023-01-16 7:59 ` Jan Beulich
2023-01-16 12:51 ` ASSI
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=0155d76115eabcc4a85f1d855b2bbd1547793e73.camel@xry111.site \
--to=xry111@xry111.site \
--cc=binutils@sourceware.org \
--cc=dje.gcc@gmail.com \
--cc=info-gnu@gnu.org \
--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).